Tours & Events
Conventions

Request IDs

Correlating requests for debugging and support

Every response includes an X-Request-Id header that uniquely identifies the request on our infrastructure. When something goes wrong, include this ID in your support ticket — it lets us jump straight to the trace in our logs instead of asking you to reproduce.

Example

HTTP/1.1 500 Internal Server Error
X-Request-Id: 7f3a1c2b-4d8e-49f0-b1e3-2c5f6a8b9d10
Content-Type: application/json
{ "error": "Internal server error" }

Sending your own ID

You may pass an X-Request-Id (or X-Correlation-Id) header on outgoing requests and we'll echo it back. Use this to correlate logs across your service and ours.

POST /api/events
Authorization: Bearer tke_live_...
X-Request-Id: my-service-2026-05-20-abc123

Keep IDs ≤ 64 ASCII characters. Anything longer is truncated. If you don't send one, the server generates a UUID v4 for you.

On this page