Configure webhooks and verify deliveries
Receive supported events on a server endpoint and handle retries safely.
Before you begin
Use a test environment and the smallest necessary access. Keep workspace API keys and signing secrets on your server, outside browser code and public screenshots.
Step by step
- 1
Prepare an HTTPS endpoint
Use a server route that can receive the documented event format. Avoid a client-side page or endpoint that exposes secrets.
- 2
Register the endpoint
Choose supported events and save the destination in the correct workspace. Store the signing secret securely.
- 3
Verify signatures
Follow the Webhooks and integration security reference in this Help Center for the exact signature headers and verification procedure before trusting or processing a payload.
- 4
Handle duplicates and retries
Use stable event identifiers for idempotency, respond promptly and do slow work asynchronously in your own system.
- 5
Inspect a test delivery
Check the recorded response and your server logs. Redact personal data and credentials from logs.
Good to know
A delivered webhook is an event notification. It does not mean your downstream business action completed successfully.
Check the result
Check the response, relevant delivery history and organisation scope. Use the Public REST API reference in this Help Center for the technical contract.
Questions & troubleshooting
Deliveries keep retrying
Inspect response status, timeout and signature verification. Do not disable signature checks just to obtain a successful response.
Rate this guide on this device. Ratings are not sent to Corthex.