Instant Webhook Endpoints

Why Use Relay Webhooks?

Webhook senders expect a fast response. If your backend is slow, down, or deploying, you risk missed events, retries, or broken integrations. Relay Webhooks sits between the sender and your application: it accepts webhooks instantly at the edge and stores them until you are ready to process them. Collect first, process later.

• Decouple collection from processing — never miss a webhook because your server is busy, restarting, or scaling up
• Respond in milliseconds — senders get an instant reply from the nearest edge location
• Buffer during disruptions — deployments, outages, and traffic spikes no longer mean lost events
• Replay at will — poll /events with a cursor, as many times as you need

Quick Start

1. Check that your hostname is available (HEAD returns 404 if unclaimed):

# 404 = available, 200 = already taken
curl -sI https://a.my-app.wh.relay.inferal.com/
HTTP/2 404

2. Claim it with your first request. The response includes your read key and domain key:

# First request returns X-Read-Key and X-Domain-Key headers
curl -si -X POST https://a.my-app.wh.relay.inferal.com/ \
  -H "Content-Type: application/json" \
  -d '{"hello":"world"}'

# Response includes:
X-Read-Key: <your-read-key>
X-Domain-Key: <your-domain-key>

3. Read events with your key:

# Poll events
curl -H "Authorization: Bearer <your-read-key>" \
  https://my-app.wh.relay.inferal.com/events

# Or stream via WebSocket
wscat -H "Authorization: Bearer <your-read-key>" \
  -c "wss://my-app.wh.relay.inferal.com/stream"

Sub-Hostnames

Need multiple endpoints under the same name? Use the domain key from your first claim to create sub-hostnames:

# Claim a sub-hostname using your domain key
curl -si -X POST https://a.staging.my-app.wh.relay.inferal.com/ \
  -H "X-Domain-Key: <your-domain-key>"

# Response includes a new read key for this sub-hostname:
X-Read-Key: <staging-read-key>

Each sub-hostname stores events independently and gets its own read key. The domain key is shared across all hostnames under one endpoint name. Without the domain key, attempts to claim under an already-owned endpoint return 409 Conflict.