Skip to main content

Webhook event types

warning

Documentation is released in preview, is not final, and may be subject to changes. Sandbox and Production environments will be available soon.

Webhook Types

The SK API currently uses these event types:

CategoryWebhook TypeWhat it does
Onboardinglegal_entity.onboardingReceive information about legal-entity onboarding status
Invoiceinvoice.outboundReceive information about invoice processing stage
Invoiceinvoice.inboundReceive information when incoming invoice is received
Credit notecredit_note.outboundReceive information about credit note processing stage
Credit notecredit_note.inboundReceive information when incoming credit note is received
Tax Data Document (TDD)tax_data_documents.outboundReceive information about tax data document processing stage
Message Level Status (MLS)message_level_status.outboundReceive information about message level status processing stage
Message Level Status (MLS)message_level_status.inboundReceive information when incoming message level status is received

The credit_note.* events carry the same payloads as their invoice.* counterparts and so on: the event type is picked from the document type, so a credit note never triggers an invoice.* event and vice versa. Subscribe to both families if you want to be notified about every document.

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.onboarding to continue an asynchronous onboarding synchronization flow.

The event tells you that something changed; the legal entity resource tells you the current state: to do that, use the GET /legal-entities/{legalEntityId} endpoint.

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 invoice.outbound, credit_note.outbound, tdd.outbound, mls.outbound events and check the document status to confirm delivery.
  • For incoming documents, use invoice.inbound, credit_note.inbound, mls.inbound 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.