Request IDs & logs

Every response includes an x-request-id header. It uniquely identifies the request in our structured logs and metrics.

Using request ids

• Log the id alongside your own request/response records.
• Include it verbatim when contacting support — we can look up the full trace in seconds.
• You may also send your own x-request-id on the request; we'll honour it end-to-end.

curl -i https://api.webrabbitmedia.com/v1/health
# HTTP/2 200
# x-request-id: 6f3c7d1e-9a2b-4c8f-b5e0-2b1a7e9d0c33
# content-type: application/json
#
# {"ok":true,"service":"webrabbit-api","request_id":"6f3c7d1e-..."}

# send your own id and we echo it back
curl -i https://api.webrabbitmedia.com/v1/health \
  -H "x-request-id: order-1024-attempt-1"

Logs & retention

Logs are retained for 30 days. Aggregate metrics (latency, status class, RPS by mode) are kept for 90 days in Cloudflare Analytics Engine and surfaced in your dashboard.