Request IDs

What is a Request ID?

Every time your client talks to the Meridian API — license checks, heartbeat pings, update queries — the response includes an X-Meridian-Request-Id header. It is a 32-character hex string that uniquely identifies that single request/response pair inside our observability pipeline.

Format

Request IDs are generated server-side using a cryptographically random source and encoded as lowercase hex. Example:

How to capture it

The Nimbus loader logs every request ID to its debug output. If you are running a debug build or have verbose logging enabled, look for lines prefixed with [req-id].

For manual inspection, use any HTTP toolkit (curl with -v, browser DevTools Network tab, mitmproxy) and copy the value from the response headers.

Including it in bug reports

When you open a support ticket or email support@getnimbus.net, paste the full request ID. One ID is usually enough — our engineers can walk the trace forward and backward from that point. If the issue spans multiple requests, include the IDs for the first failing request and the last successful one.

Privacy

Request IDs do not encode any personally identifiable information. They are opaque random identifiers used solely for internal tracing. Sharing a request ID with our support team does not expose your license key, hardware fingerprint, or any other sensitive data.