Debugging requests
In addition to error codes returned from API responses, it may sometimes be necessary to inspect HTTP response headers as well. Of particular interest will be the headers which contain the unique ID of a particular API request, and information about rate limiting applied to your requests. Below is an incomplete list of HTTP headers returned with API responses:openai-organization
: The organization associated with the requestopenai-processing-ms
: Time taken processing your API request
openai-version
: REST API version used for this request (currently 2020-10-01
)
x-request-id
: Unique identifier for this API request (used in troubleshooting)
x-ratelimit-limit-requests
x-ratelimit-remaining-requests
x-ratelimit-remaining-tokens
x-ratelimit-reset-requests
OpenAI recommends logging request IDs in production deployments, which will allow more efficient troubleshooting with our support team should the need arise. Our official SDKs provide a property on top level response objects containing the value of the x-request-id
header.Access raw response objects in SDKs#
If you are using a lower-level HTTP client (like fetch or HttpClient
in C#), you should already have access to response headers as a part of the HTTP interface.If you are using one of OpenAI's official SDKs (which largely abstract the HTTP request/response cycle), you will need to access raw HTTP responses in a slightly different way.Below is an example of accessing the raw response object (and the x-ratelimit-limit-tokens
header) using our Python SDK.Here is how you'd access a raw response (and the x-ratelimit-limit-tokens
header) using our JavaScript SDK. Modified atΒ 2024-12-11 08:04:40