Skip to main content

HTTP Response Codes

There are two places HTTP status codes matter in Webhookr: the response Webhookr returns when you send a webhook (ingestion), and the response a destination returns when Webhookr forwards an event (delivery).

Ingestion — codes Webhookr returns​

When you POST to /v1/ingest/<slug>:

CodeMeaning
202 AcceptedEvent received and stored. The normal success response.
400 Bad RequestThe slug is malformed (wrong characters or too long).
404 Not FoundNo active endpoint matches the slug.

202 is intentional: Webhookr stores the event synchronously and delivers to destinations asynchronously, so a 2xx here means "stored," not "delivered."

Delivery — codes destinations return​

When Webhookr forwards an event to a destination, the destination's response decides the delivery status:

Destination responseDelivery result
2xx (200–299)SUCCESS
3xxFAILED — redirects are not followed as success.
4xxFAILED — the destination rejected the request.
5xxFAILED — the destination errored; often transient.
No response (timeout)FAILED
Connection / DNS / TLS errorFAILED

Guidance​

  • 401 / 403 — the destination expects authentication. Add the right headers to the destination.
  • 404 — the destination URL is wrong or the route doesn't exist.
  • 5xx or timeout — likely transient; replay after the service recovers.