Ship webhooks. Not retry logic.

POST an event. We handle retries, HMAC signing, exponential backoff, per-endpoint concurrency, and durable receipts. You handle your product.

Get an API key curl relayapi.dev/quickstart

~ / relay / send-event.sh

# fire an event — we handle the rest
$ curl -X POST https://api.relayapi.dev/v1/events \
    -H "Authorization: Bearer rk_live_..." \
    -H "Content-Type: application/json" \
    -d '{
      "endpoint_id": "ep_9f2a",
      "type": "order.paid",
      "data": { "order_id": "o_1029" }
    }'

→ 202 Accepted
{ "event_id": "evt_2Q8h...", "status": "queued" }

uptime · 30d

99.998%

p50 delivery

184ms

p99 delivery

1.2s

retries handled

12.4M/wk

// features

Just the primitives you'd build yourself.

If you've written a webhook system before, you know the list. Here it is, managed.

Retry with backoff

8 attempts over 24h. Exponential curve. Per-endpoint override.

HMAC-SHA256 signing

Relay-Signature: t=<unix>,v1=<hex>. Verify in ~5 lines.

Attempt logs

Every attempt: status, headers, body, latency. Queryable via API.

Idempotency keys

Send the same event twice, we deliver it once. Server-side dedup.

Concurrency caps

Cap in-flight deliveries per endpoint. Never DoS your own customer.

Circuit breaker

Endpoint 4xx-storming? We back off automatically and alert.

This is a SiteGuide demo page. The chat bubble in the bottom-right is the embeddable widget loaded with data-site="relayapi". Try asking it: "How do I send my first event?", "How does the retry policy work?", or "How do I verify signatures?"