Update AdditionalTaxIdentifier in Storecove

What this operation does

Update AdditionalTaxIdentifier

• PATCHChanges data · AdditionalTaxIdentifiersapi.storecove.com/legal_entities/{legal_entity_id}/additional_tax_identifiers/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Storecove operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Storecove operations

• Create a new received documentPOST · changes data
• Create a new LegalEntityPOST · changes data
• Submit a new invoicePOST · changes data
• Submit a new documentPOST · changes data
• Create a new AdministrationPOST · changes data
• Create a new PeppolIdentifierPOST · changes data
• Receive a new DocumentPOST · changes data
• Create a new AdditionalTaxIdentifierPOST · changes data

All 30 Storecove operations

Questions

Can HumDay update additionaltaxidentifier in Storecove?

Yes. This operation is published in Storecove's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Storecove data?

Yes — this is a PATCH operation, so it changes something in Storecove. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Storecove account.

Where this came from

Read from a published API description for Storecove at www.storecove.com/api/v2/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.