Webhook Event Types

Webhook Types

The UAE API currently uses these event types:

• legal_entity.synchronized: a legal entity synchronization step has completed.
• document.received: an incoming invoice or credit note is available.
• document.delivered: an outgoing invoice or credit note has completed delivery.

Subscribe only to the events your application handles. The API Reference remains the source of truth for the supported event catalogue and payload contract.

Onboarding Events

Use legal_entity.synchronized to continue an asynchronous onboarding or capability synchronization flow. Read the legal entity again with GET /legal-entities/{legalEntityId} and check its status, enabled capabilities, and synchronization timestamps.

The event tells you that something changed; the legal entity resource tells you the current state.

Invoice Lifecycle & Events

Document processing is asynchronous. A successful POST creates the resource first; validation, Peppol exchange, and tax reporting continue afterwards.

• For outgoing documents, use document.delivered and the document status to confirm delivery.
• For incoming documents, use document.received to retrieve and import the new resource.
• If a webhook is delayed, use the collection and detail endpoints as a fallback.

Keep exchange and tax reporting as separate status concepts. A document may be delivered while tax reporting is still processing, or one of the two operations may fail independently.