Skip to main content

Access & Setup

Requesting Webhook Access​

Webhook access isn't turned on by default — it's enabled per account on request. To get started, contact devops@celitech.com or your CELITECH account manager and ask to have webhooks enabled for your account.

note

If you navigate to Developers → Webhooks in the CELITECH Dashboard before access has been enabled, you'll see: "Webhooks are not enabled for your account. Please contact devops@celitech.com to enable Webhooks for your account."

Once enabled, the Webhooks section becomes available under Developers in the dashboard, where you can register and manage your endpoint.

Developers section with the Webhooks entry point

Registering Your Endpoint​

From Developers → Webhooks, add a new endpoint and fill in:

  1. Endpoint URL — the URL you want CELITECH to send events to.
  2. Description (optional) — a note to help you identify this endpoint later.
  3. Subscribe to events — check which event type(s) you want to receive. See the Event Catalog for what's available.

Your endpoint URL should:

  • Be a public HTTPS URL. CELITECH cannot deliver to endpoints on localhost or behind a firewall/VPN.
  • Respond quickly with a 2xx status code — within about 15 seconds. Do the minimal work needed to accept the request (e.g. verify the signature and enqueue it for processing) before responding — see Delivery & Retries below for what happens if you don't.

Endpoint registration screen

Managing Your Webhook Endpoints​

The Webhooks section of the dashboard lets you:

  • View and edit your registered endpoint URL
  • View and change which event(s) you're subscribed to
  • Access your signing secret, used to verify webhook signatures
  • View a log of recent deliveries and their status
  • Send an example event to your endpoint to test your integration before relying on it in production — see Testing Your Integration

Webhook endpoint management and delivery log

note

Treat your signing secret like any other credential — keep it out of client-side code and version control.

Delivery & Retries​

If your endpoint doesn't respond with a 2xx status — whether it returns an error, times out, or doesn't respond at all — the delivery is automatically retried with increasing delay between attempts, over a period of hours. You don't need to implement your own retry logic on the receiving end. If your endpoint continues to fail for an extended period, retries eventually stop and the endpoint may be disabled — keep an eye on your delivery log so you notice before that happens.

Because retries can result in the same event being delivered more than once, always process deliveries idempotently — see Verifying Webhook Signatures for how to de-duplicate using the delivery identifier.