Skip to main content
POST

Receive an event

Method: POST | Endpoint: /v1/events/{token} Description: The URL a connected app (Recharge, your own system, or a no-code tool such as Zapier or Make) posts its events to. An event that matches an active workflow’s “Webhook received” trigger starts a run. See Inbound events for setup. Authentication: No API key. The token in the path (ibev_ followed by 64 hex characters, copied from the event source in the dashboard) identifies the source. A signed source must also send its signature header: Recharge sends X-Recharge-Hmac-Sha256; a generic signed source sends X-iBubbl-Signature: t=<unix seconds>,v1=<hex>, an HMAC-SHA256 of {t}.{raw body} with the source’s signing secret, no more than 5 minutes old. A secret-URL source sends no signature and is limited to 60 requests a minute.

Request Body

Responses

200 OK
Every request that passes the signature check gets 200, including one that starts no run (runs_started: 0), so the sending app never retries or disables the hook. The reason an event started nothing is recorded on the event source. 403 Forbidden
The signature header is missing or doesn’t match. 404 Not Found
The token is malformed, unknown or revoked. 413 Content Too Large
429 Too Many Requests
Only a secret-URL source over 60 requests a minute while a workflow is listening on it. Without a listener, the extra events are dropped with 200.

Path Parameters

token
string
required

Response

Event accepted.

received
boolean
required

Always true once the signature has been verified.

Example:

true

runs_started
integer
required

How many workflow runs this event started. 0 is a normal answer — it means no active workflow's trigger matched, or this event was a redelivery that de-duplicated onto an existing run.

Example:

1