Webhooks
The public design site does not currently expose a webhook subscription or delivery API. Agents and integrations should read the public resources directly and must not invent event names, callback URLs, signing secrets, retry schedules, or delivery guarantees.
Required contract for a future integration
Any future Thorbis webhook surface must document event versioning, subscription scope, signature verification, timestamp tolerance, replay protection, idempotency, ordering, retry and backoff, timeout behavior, redelivery, payload examples, permissions, test events, observability, deletion, and degraded-state behavior before it is considered usable. The user interface must show whether delivery is active, delayed, failing, or revoked.
Integration partners should contact partners@thorbis.com. Product-account questions belong with support@thorbis.com. A response from either address is not itself an API credential or permission to probe private endpoints; use only an explicitly documented and provisioned integration.