> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/advanced-features/request-tracing-and-debugging.md). # Request Tracing and Debugging Every OCPI request flowing through ENAPI carries tracing headers that let you correlate a specific request across your system, ENAPI, and your partner's system. When something goes wrong, these IDs are the fastest path to resolution. ### The tracing headers * **`X-Request-ID`:** Unique per HTTP request. Identifies one specific call. * **`X-Correlation-ID`:** Shared across related requests. Links a chain of calls that belong to the same logical operation. ENAPI generates a new `X-Request-ID` for each forwarded request (per OCPI spec), so the request ID you send is different from the one your partner receives. `X-Correlation-ID` is preserved across the entire chain, which is why it's the right ID to share when coordinating with a partner. ### Debugging a problem 1. Capture the `X-Request-ID` and `X-Correlation-ID` from the response showing the issue. 2. Share the IDs with ENAPI support; we can trace the request's full path. 3. Share the correlation ID with your partner so they can find their side of the trace. ### Best practices * Setting both headers on every request is strongly recommended so the IDs appear in your logs from the moment the request fires. If you omit them, ENAPI generates UUIDs internally, but you'll only see them in the response. * Use UUIDs for both `X-Request-ID` and `X-Correlation-ID` values. * Log both headers for every request and response on your side. * When reporting an issue, always include the correlation ID. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enapi.com/advanced-features/request-tracing-and-debugging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.