Browse documentation
Core concept
Receive events
Hooks accepts JSON and form-encoded payloads over HTTPS. It records the raw body and headers before applying verification rules, so you can inspect exactly what arrived.
Request headers
| Header | Description |
|---|---|
X-Hooks-Signature | Timestamp and HMAC signature for the raw body. Verify this before processing. |
X-Hooks-Event | Unique event ID, useful for logging and support. |
X-Hooks-Delivery | Unique delivery ID. Reuse it as an idempotency key at your destination. |
Content-Type | application/json or application/x-www-form-urlencoded. |
Response behavior
Hooks returns 202 as soon as the event is persisted. It does not wait for your downstream services. A 4xx response means the request was rejected and no event was created; check the endpoint’s verification rules and signature configuration.
Use the raw request body when computing signatures. Re-serializing JSON can change whitespace and key order, producing a false mismatch.
Was this page helpful?
Tell us if something was missing or unclear.
Ready to try it?Create a free workspace and send your first event.