An event reaches your address, signed.
When a case is opened, a hearing changes or a document is uploaded, a signed notification goes to your accounting, document or reporting system. With your API key you reach the same data from your own software.
The events you listen to
Sample subscription; you choose the states.
| Resource | Created | Updated | Deleted |
|---|---|---|---|
| Case | On | On | Off |
| Hearing | On | On | On |
| Document | On | Off | Off |
With your API key you reach case, client, hearing, document and invoice data from your own software; access is limited to the permissions of the user who created the key.
01/03
The delivery log.
Every notification is signed with a key specific to the subscription, and every delivery attempt is recorded. If your address does not answer, the notification is retried; on the subscription screen you see which one was delivered and when.
Test dispatch
DeliveredThe test notification sent with Trigger was received.
Hearing updated
DeliveredSent to your address.
Document uploaded
Will retryYour address did not answer; the notification will be retried.
Document uploaded
DeliveredRetry: your address received the notification.
Case deleted
FailedThe address refused the connection; it shows on the subscription screen.
Sample log; addresses and times are for illustration.
- Signed
- Every request is signed with a key specific to the subscription; your system verifies it.
- Retry
- A notification that cannot be delivered is retried automatically.
- Test
- You try your address with one click, without waiting for a live event.
- Record
- The result of every attempt is listed on the subscription screen.
02/03
A subscription is set up in five steps.
You choose which event goes to which address. Only encrypted addresses are accepted, and only authorised users see and change subscriptions.
09:20 Enter the address and the events
Sample screens; addresses and values are for illustration.
03/03
What do teams ask about webhooks and the API?
- 01/08
Which events trigger a webhook?
A notification is sent when case, hearing and document records are created, updated and deleted. In your subscription you pick only the events you need.
- 02/08
How do I know a notification comes from HukukBis?
Every notification is signed with a key specific to the subscription. Your system verifies the signature to confirm that the notification came from HukukBis and was not altered; you can reject requests that cannot be verified.
- 03/08
What happens if a notification cannot be delivered?
The system retries the notification and writes the result of each attempt to the delivery record. On the subscription screen you can see which notification was delivered.
- 04/08
How do I get an API key?
The API and webhooks are part of the Corporate plan. The firm administrator creates an API key in Settings and can revoke or renew it at any time. Technical integration documentation is provided to customers separately.
- 05/08
Which data can I reach through the API?
Case, client, hearing, document and invoice data. Requests stay within the permissions of the user who created the key: a record you are not allowed to see is not visible through the API either. You manage permissions on the roles and permissions screen.
- 06/08
Can another firm's data reach my address?
No. Each company's subscriptions and API access cover only its own data. The separation of data and the assurance model are described on the security page.
- 07/08
What do teams typically build with webhooks and the API?
Passing issued invoices to accounting software, combining case and collection data in internal reporting dashboards, mirroring new clients in a CRM, copying uploaded documents to a corporate archive and forwarding hearing changes to team chat tools. For the other connectors see integrations.
- 08/08
Where do the records behind the webhook events live?
Case, hearing and document records are kept in case management; every change to a record is sent to your address according to the events you selected.