POST to an HTTPS URL you control, retries it if your server doesn’t answer, and logs every attempt.
Events
Each endpoint subscribes to the events and brands you choose. See Events for every payload.
What a delivery looks like
The envelope
Every event has the same outer shape. Onlydata differs by event type.
Payloads are deliberately small: ids, outcomes and a link. Fetch the full record from the API with your own key when you need it. Deliveries never carry prompts, answer text or credentials.
Headers
How your endpoint should respond
1
Verify the signature
Check
X-Quotable-Signature against the raw body before you trust anything in it. Reject deliveries whose timestamp is more than 5 minutes from your clock.2
Deduplicate on the event id
Deliveries are at-least-once. Store each
id you’ve processed and skip repeats.3
Answer 2xx within 10 seconds
Any
2xx status counts as delivered. Do slow work after you respond, for example on a queue.3xx (redirects are never followed), 4xx or 5xx status, a timeout after 10 seconds, or a connection error. See Delivery and retries.
Requirements
- The URL must use
https://and be reachable from the public internet. Private and internal addresses are refused. - The URL can’t contain a username or password. Authenticate deliveries with the signature instead.
- A workspace can have up to 10 endpoints.
- Only the workspace owner and integration admins can add or change endpoints. Every member can see them and their delivery logs.
Next steps
Events
Every event type with its full payload.
Verify signatures
Copy-paste verification for Node.js and Python.
Manage endpoints
Add, pause, rotate and redeliver from Settings.
Slack alerts recipe
Post daily visibility scores to a Slack channel.