How the relay works

Prefix your destination URL with https://relay.requ.es/. The relay forwards it and records the destination’s status and latency.

1. Send your first request
Sign in, then create a key in Settings, API keys. Copy the key from the key list any time.
URLhttps://relay.requ.es/<destination>
Everything after the slash is forwarded as is, minus any x-requ-* headers and query params.
Authx-requ-api-key
Header or query param. Pass your API key with every request.
```
curl -X POST \
  -H 'x-requ-api-key: requ_live_YOUR_KEY' \
  -H 'content-type: application/json' \
  -d '{"name":"hello"}' \
  https://relay.requ.es/https://httpbin.org/post
```
2. Inspect a request
New requests show up in Requests as they arrive. Open a row to see headers, body, and timing. Body panels switch between Pretty and Raw. Each request has a stable URL you can send to a teammate on your workspace.
200 OK
Success
301 RDR
Redirect
404 ERR
Error from the destination
Relay failed: the destination never responded. ERR
The destination never responded, counted under No status
PENDING
Waiting for the destination
3. Replay a request
Open a request and select Replay. Edit the method, path, headers, or body; a diff tab shows your edits against the original before you send. Select Send or press ⌘Command Enter or Ctrl Enter. The replay arrives as a new request linked to its source.

Limits and retention

Larger response bodies are cut at the cap and marked; larger request bodies are not stored. Replays are requests too, with their own 7-day window.