To aid in integration with Semantik you can subscribe to certain events that occur within the system. The event details are sent via webhook to an address that you specify.
Managing Event Settings
The Semantik Public API page lists the endpoints available for managing event configuration.
Event data will be sent to the configured receiver as an HTTP POST call. If the receiver responds with an HTTP status code in the range 200-299 within the timeout period the webhook call is considered successful.
The following conditions are considered failures and will be retried:
More than 5 redirect responses (HTTP status 301 or 308) are received from the server.
The receiver responds with an HTTP status code outside the 200-299 range.
The receiver does not respond within the timeout period of 90 seconds.
A network error is encountered (DNS lookup failure, network-not-available, etc.).
Failed webhook calls are retried as follows:
Approximate Delay (from previous attempt)
If all retries fail, the event is silently discarded.
Event Body Structure
All events are sent in a standard JSON envelope:
ID of the tenant the event applies to.
A code which uniquely identifies the event.
A human-readable description of the event. NOTE: Unlike the code property, description is for human consumption only and is subject to change without warning.
“Document requires manual review”
Contains detail information about the event.
See Event Types section below.
Document Requires Manual Review
Sent when a document enters a manual review state.
ID of the ingestion containing the document.
Zero-based index of the document within the ingestion.
Source of ingestion.
ID assigned to the document by Semantik.
The original physical file name of the document.
Example webhook body:
"description": “Document requires manual review”,
The following special headers will be included with every call:
Uniquely identifies the event - the value of this header remains consistent even if the HTTP call is retried due to a failure.
NOTE: While unlikely, there is a possibility that duplicate events may be sent with different X-Request-Id values.
The attempt number. This will be “1” for the initial request and will be incremented by one each time the call is retried.