Webhooks

Recerc webhooks are a simple ingestion endpoint that lets external systems send events into a workspace using a webhook handle.

Endpoint

POST /api/webhooks/{workspace_id}/{webhook_id}

• workspace_id: the workspace handle/id you were given
• webhook_id: the event/webhook handle you were given (each handle can have its own expected payload shape)
• authentication: an API key in the required format

Authentication

Use an API key either as a bearer token header:

curl -X POST "https://recerc.com/api/webhooks/<workspace_id>/<webhook_id>" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Idempotency-Key: <OPTIONAL_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"hello":"world"}'

Or as a query parameter:

curl -X POST "https://recerc.com/api/webhooks/<workspace_id>/<webhook_id>?token=<API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"hello":"world"}'

Payload

The shape of each event depends on the configuration of the {workspace_id} + {webhook_id} pair.

Send a single JSON object.

{
  "any": "shape",
  "dependsOn": "your integration"
}

Responses

200 OK

Returns a single id plus processing information.

Idempotency (optional)

If you provide an Idempotency-Key header, Recerc will deduplicate retries:

• If the same key was already used for the same {workspace_id} + {webhook_id} and the server previously returned 200, subsequent requests will return the same 200 JSON response without re-processing.

Errors

• 401: missing API key
• 403: invalid API key
• 404: invalid {webhook_id} (unknown handle)
• 400: invalid request parameters
• 500: internal error

OpenAPI Reference

For the full schema (including request/response examples), see:

• /docs/specs/webhooks