Webhook integration: automatic re-delivery, delivery log, data transfer
VetBis tells your own system about an event in the clinic through a webhook. You define the target address; if delivery fails it is tried again automatically, repeated failures pause the subscription, and every attempt is logged. For moving from your current program there is the data migration wizard, and for the state of official connections the e-invoice and ATS/ITS pages.
- Source
- Delivery
- Status
Live flowDelivered 8 / 8
Steps
- 1An event occursA record changes in the clinic and the event is lined up for delivery.
- 2Delivery startsThe event is sent to the configured target address.
- 3Target does not respondThe first attempt fails and a new attempt is planned.
- 4Second attemptThe target still does not respond.
- 5Third attemptStill no reply from the target.
- 6Subscription suspendedAfter repeated failures delivery stops and the suspended state is logged.
- 7Re-enabledOnce the target is fixed the subscription is re-enabled and delivery is tried again.
- 8DeliveredThe successful delivery appears in the delivery log.
Event, delivery, failure, re-delivery, suspension
Watch step by step what happens when your target system stops responding. Failed deliveries are tried again automatically; after repeated failures the subscription is suspended and shows in the delivery log. Event names are examples.
Subscription: appointment events
- appointment.createdSample event · target not respondingDelivered
- patient.updatedSample event · target healthyDelivered
Live flowDelivered 8 / 8
Steps
- 1An event occursA record changes in the clinic and the event is lined up for delivery.
- 2Delivery startsThe event is sent to the configured target address.
- 3Target does not respondThe first attempt fails and a new attempt is planned.
- 4Second attemptThe target still does not respond.
- 5Third attemptStill no reply from the target.
- 6Subscription suspendedAfter repeated failures delivery stops and the suspended state is logged.
- 7Re-enabledOnce the target is fixed the subscription is re-enabled and delivery is tried again.
- 8DeliveredThe successful delivery appears in the delivery log.
How a webhook subscription is managed
A subscription is just a target address for an event type. VetBis handles the rest.
Event-based subscription
You define the event type and the target address.
Active, inactive, suspended
You change the subscription state; after repeated failures the system suspends the subscription.
Retries
A failed delivery is tried again automatically a limited number of times.
Delivery log
The result and state of every attempt appear in the delivery log.
Move data from your current program: CSV import
A webhook pushes data out of VetBis. For moving in from your current program there is an import wizard that works with a CSV file: you upload the file, map the columns, and rows are validated before the import.
- File
- Mapping
- Validation
- Import
| 1 | Jane Sample | |
| 2 | John Demo | |
| 3 | (name missing) | Required field empty |
2 rows ready, 1 row with an error
Integration status: which connection is ready today?
For official and messaging providers, records are kept in VetBis but the external provider connection is not set up yet. The table below shows the real state today.
| Connection | Status | What it means |
|---|---|---|
| Webhook | Working | Event-based subscription, automatic re-delivery and the delivery log work. |
| CSV import, CSV, XLSX and PDF export | Working | The data migration wizard and report export work. |
| GIB e-documents | In preparation | Document records are kept; the official submission connection is being prepared. |
| ATS and ITS | In preparation | Filing records are kept; the official service connection is being prepared. |
| IYS | In preparation | Contact consents are recorded in VetBis; IYS registration is being prepared. |
| SMS | In preparation | Messages are recorded; the Netgsm adapter is in place and sending works once the platform key is configured. |
| In preparation | Messages are recorded; the adapter for the clinic's own Meta WhatsApp account is in place and sending works once the clinic connects its account. | |
| In preparation | Messages are recorded; the Resend adapter is in place and sending works once the platform key is configured. | |
| Mobile notification (push) | In preparation | Notifications are recorded; the provider connection is being prepared. |
Sharing data with your accountant
When you work with an accountant, you share your data as files.
Pages to read alongside integrations
Frequently asked questions about integrations
The connections that work today are event-based webhooks, CSV import, and CSV, XLSX and PDF export. For GIB e-documents, ATS and ITS, IYS and mobile notifications, records are kept and the provider connections are being prepared. The SMS, e-mail and WhatsApp adapters are in place in the code, and sending works once the provider key or the clinic's account is configured. The current table is on this page.
You define a target address for an event type. When the event occurs, VetBis delivers it to the target. A failed delivery is tried again automatically, repeated failures suspend the subscription, and every attempt shows in the delivery log.
We do not announce public API documentation or a test environment. Tell us your integration need and we will define the scope together.
No. You can export reports as XLSX and PDF and customer and patient lists as CSV, and share them with your accountant.
With the import wizard that works with a CSV file: you upload the file, map the columns, and rows are validated before the import. Details are on the data migration page.