Skip to Content
CerebrumDocs
GuidesAPI referenceTrust & security

Response Requirements

For a webhook delivery to be considered successful, your endpoint must:

  • Return an HTTP 2xx status code in the 200-299 range. 200 OK, 200 with a duplicate acknowledgement body, and 204 No Content are all valid choices.
  • Acknowledge promptly, with an implementation target of under 10 seconds after durable acceptance. A timeout is a failed attempt and can be retried.
  • Treat the response body as optional. Its content is not used to determine success.

Any non-2xx response, including a 3xx redirect, 4xx response, or 5xx response, is a failed delivery attempt. Return 2xx only after the notification is safely stored. A 2xx response whose body says that processing failed is still a successful delivery acknowledgement.

Deployment timeout is unconfirmed

Svix's receiving introduction documents a 30-second response window, while its current webhook reliability overview and webhook architecture overview describe 15 seconds. The applicable Cerebrum deployment deadline is not established by the reviewed API source. Do not treat either published value as a Cerebrum-specific guarantee. Persist and acknowledge immediately where possible, well within the recommended 10-second target, and perform resource retrieval asynchronously.

A duplicate svix-id can receive a successful response without being processed again, provided the earlier delivery was durably recorded. Do not acknowledge a new event before its inbox write commits.

Successful responses

HTTP/1.1 204 No Content

A duplicate already present in the durable inbox can instead return:

HTTP/1.1 200 OK
Content-Type: application/json

{"status":"duplicate"}

See Delivery and retry policy and the durable receiver example.

On this page