Event delivery
RevDesk webhooks
Receive signed RevDesk call, message, and task events with documented verification, retry, idempotency, and recovery behavior.
What it is
RevDesk webhooks let integrations react to completed calls, messages, tasks, and other lifecycle events without repeatedly polling the REST API. A webhook consumer should authenticate the event before parsing it, acknowledge accepted deliveries quickly, deduplicate retries with the stable event identifier, and move slow work into its own queue. The public documentation and OpenAPI contract describe the supported event and endpoint-management surfaces.
When to use RevDesk webhooks
- Synchronize call, message, or task outcomes into another system as they happen.
- Wait for long-running work without spending rate-limit budget on polling.
- Build a durable event consumer that can tolerate duplicate or out-of-order delivery.
Recommended workflow
- 1Create a narrowly scoped webhook endpoint and store its signing secret securely.
- 2Verify the signature against the raw request body before processing the event.
- 3Acknowledge promptly, deduplicate by event ID, and make downstream handlers idempotent.
Safety and approval boundaries
- Do not trust an event solely because it reached the configured URL.
- Return a successful acknowledgement only after the event is durably accepted.
- Never log credentials, full sensitive payloads, or unredacted call content by default.
