Webhooks allow receiving Push events programmatically from the Backoffice as soon as they happen. The use cases differ from one user to another and enable the connection to 3rd party applications. These Webhook implementations can be easily specified in the Backoffice (Check out Creating Webhooks ).
All events are queued in our system and sent first in first out until a success HTTP code is returned, see below.
Event Types
The following event types are available, in chronological order when they are emitted during a sales process
| Event Type | Event Name | Description |
|---|---|---|
| Article | Article booked / cancelled | An event-based push of data specifying booked articles |
| Invoice | Invoice created / cancelled | An event-based push of new or cancelled Invoices |
| Shift Ended | Shift ended | An event-based push of data specifying an ended shift |
HTTP Responses
In order to pass on success and errors through the system, we expect the following HTTP responses
| HTTP code | HTTP response | Description |
|---|---|---|
| 2xx | OK | Successfully transmitted, cleaned from our queue |
| 4xx | Malformed data / client error | Failed to transmit data due to malformed/ missing data, event remains in queue and will be tried again |
| 5xx | Server Error | Failed to transmit event due to a server error on the receiving end, event remains in queue and will be tried again |