The webhook registry enables seamless integration with third-party accounting systems by automatically sending orders directly to them, ensuring accurate and efficient financial tracking and management.
Create New Registry
In the Ventrata dashboard, go to Supplier Settings > Registries.
Press the + New Registry button.
Select Webhook Registry.
Enter a name for the registry.
Enter the URL each order will be posted to.
Select the types of ledger entries to be included.
Select the columns by which ledger entries will be grouped.
Press the Create Registry button.
Webhook Request
Every time an order is confirmed, updated or cancelled the webhook endpoint will be called. The request will be an HTTP POST request, and the body will look like this:
{
"order_id": "2e7f2d6f-0473-4935-8cfb-c11b2caa6dab",
"registry_data": {},
"idempotency_key": "5ffd8c8c-19d5-4999-8c9b-475dabeb45f5",
"ledger_entries": [
{
"ledger_code": null,
"currency": "EUR",
"quantity": 0,
"debit": "38.0",
"credit": "0.0",
"description": "Cashflow"
},
{
"ledger_code": null,
"currency": "EUR",
"quantity": 2,
"debit": "0.0",
"credit": "22.0",
"description": "Museum General Admission"
},
{
"ledger_code": null,
"currency": "EUR",
"quantity": 2,
"debit": "0.0",
"credit": "16.0",
"description": "Museum Child Ticket"
}
]
}The object will always contain the following keys:
Key | Description |
| a unique ID that identifies the order (UUID) |
| the last response of the webhook request |
| a unique key for this request; if the request fails it will be retried with the same |
| a list of ledger entries for this order |
Each ledger entry is defined as:
Ledger Parameter | Description |
| the ledger code for the entry |
| this field and any other columns included in |
| a positive integer for revenue ledger entries |
| increase the value of asset, expense and loss accounts |
| increase the value of liability, equity, revenue and gain accounts |
| is the human readable description of each line item |
The data your endpoint responds with will be saved against the order, and will be sent back to you in a future request if the order is subsequently modified in the registry_data field.
Every time your endpoint is called, the response will overwrite the registry data on the order and the new value will be sent to your endpoint in the next request.