Webhooks & Events

Buyer delivery

Delivery to a buyer is an HTTP POST to the endpoint configured on their offer. The payload format, headers, and credentials are per-endpoint configuration.

A buyer's response determines the outcome. Endpoints are configured with patterns matching accept, reject, duplicate, and error responses, so a buyer's existing response format usually works without change on their side.

An offer may have several endpoints, tried in sequence. Only the first decides accept or reject; the remainder are notified.

Seller postbacks

When a lead sells, a postback can fire to a URL you configure — useful for attributing revenue back to the traffic source that generated it.

Timeouts and failures

Each delivery attempt is bounded by a timeout. A buyer endpoint that fails repeatedly is skipped for a cooldown rather than being retried indefinitely, so one unhealthy buyer doesn't slow distribution for everyone.

Every attempt is logged with the request, the response, and the timing.

Status codes buyers should return

Distinguishing reject from error matters: a reject is a normal outcome, an error counts toward the failure threshold that opens the circuit breaker.