Register a webhook destination
Register one HTTPS destination for terminal render events. The URL must pass the same egress policy the platform applies to every outbound request: public HTTPS on port 443, no credentials, and a DNS answer set of public addresses only. Delivery rechecks all of it on every connection, so a name that later resolves privately is refused then too. The signing secret is returned in this response and never again. Every delivery carries a Thirds-Signature header of the form "t=<unix-seconds>,v1=<hex>": each v1 value is HMAC-SHA256 over the exact bytes "<t>.<body>" with one signing secret, so verify against the raw body before parsing it, and refuse a timestamp too far from your own clock to bound replays. During a rotation overlap the header carries two v1 values (the current secret's first, then the previous secret's), and a receiver accepts the delivery when any one value matches. See the webhook delivery guide for a worked receiver that verifies this header in Node or Python.
Request
- Base URL: https://thirds.ai
- URL: https://thirds.ai/v1/webhooks
- Auth: HTTP bearer
Request body
Response
The destination was registered and is enabled. This is the only response, with rotation's, that ever carries the signing secret.
Changes
No recorded changes to this operation across all 1 revision of this API.