Sending events in

The ingest URL

Send events with an HTTP POST to your source's ingest URL. The body is stored exactly as received, any content type is accepted, and the maximum body size is 1 MB. A successful call returns 200 OK with the stored event's ID.

Terminal

curl -X POST https://webhooker.eu/in/YOUR_SOURCE_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"event":"order.created","id":"evt_123"}'

# 200 OK
# {"id":"3f9c2a10-8b1e-4c7a-9f2d-1a2b3c4d5e6f"}

The returned id is the event's identifier in Webhooker — the same value we later send to your destinations in the X-Webhooker-Event-Id header, so you can correlate an inbound event with its deliveries.

Owning the ingest URL is what makes Webhooker a webhook gateway rather than a proxy: the event is stored here first, and everything downstream reads from that record. For the wider picture of how a webhook travels end to end, start with the walkthrough.

Response codes

Status	Meaning
`200 OK`	Event accepted and stored durably. Body: `{"id":"…"}`.
`401 Unauthorized`	Inbound signature verification failed. The event is still stored (for audit) but is not delivered. Body carries `error.code = signature_invalid`.
`404 Not Found`	The source token is unknown or the source was deleted.
`413 Payload Too Large`	The request body exceeds the 1 MB limit.
`429 Too Many Requests`	The source exceeded your plan's ingest rate. A `Retry-After` header tells you how many seconds to wait.

Note

A 401 means the request reached Webhooker but its signature didn't check out. We keep the event for your audit trail, so a run of 401s in the log usually points at a misconfigured secret rather than a lost payload. See Inbound verification.