Webhooks
Webhooks tell your server the moment something happens in Incapon: when a monitored page changes, when a PDF's OCR finishes, when a signature comparison is decided, when an Altyazı job completes or when your credit balance runs low. Instead of building polling loops, you define one HTTPS endpoint and events arrive there as signed JSON.
How It Works
Each team can have one or more webhook endpoints, and each endpoint receives only the events it selected. When an event occurs, Incapon sends the request as a POST and expects a 2xx response within 10 seconds. The request body is signed with HMAC-SHA256 using your whsec_... secret; the signature travels in the X-Incapon-Signature header, the timestamp in X-Incapon-Timestamp and the unique event id in X-Incapon-Event-Id.
If no response arrives or a code other than 2xx comes back, the event is held in the queue and tried 8 times in total at growing intervals over about two days. Events that still fail can be resent from the dashboard with one click. Webhook delivery is free; credits are only spent on the operation that triggered the event.
Pages in This Section
| Page | What it covers |
|---|---|
| configuration | Creating an endpoint, choosing events, the secret and test dispatch. |
| signature-verification | Verifying with HMAC-SHA256 that an incoming request really came from Incapon. |
| event-types | Every event type and an example JSON payload for each family. |
| retry-policy | The retry schedule, idempotency, replay and automatic disabling. |
Start setup with Webhook Configuration, then be sure to add signature verification before going live.