Responses
API key as bearer token in Authorization header
Request schema for Responses endpoint
Input for a response request - can be a string or array of items
[{"role":"user","content":"What is the weather today?"}]falseautoPossible values: autofalseDEPRECATED Use providers.sort.partition instead. Backwards-compatible alias for providers.sort.partition. Accepts legacy values: "fallback" (maps to "model"), "sort" (maps to "none").
A unique identifier representing your end-user, which helps distinguish between different users of your app. This allows your app to identify specific users in case of abuse reports, preventing your entire app from being affected by the actions of individual users. Maximum of 128 characters.
A unique identifier for grouping related requests (e.g., a conversation or agent workflow) for observability. If provided in both the request body and the x-session-id header, the body value takes precedence. Maximum of 128 characters.
Successful response
Bad Request - Invalid request parameters or malformed input
Unauthorized - Authentication required or invalid credentials
Payment Required - Insufficient credits or quota to complete request
Not Found - Resource does not exist
Request Timeout - Operation exceeded time limit
Payload Too Large - Request payload exceeds size limits
Unprocessable Entity - Semantic validation failure
Too Many Requests - Rate limit exceeded
Internal Server Error - Unexpected server error
Bad Gateway - Provider/upstream API failure
Service Unavailable - Service temporarily unavailable
Infrastructure Timeout - Request timed out at our edge network
Provider Overloaded - Provider is temporarily overloaded
Last updated
Was this helpful?

