Create response with OpenAI/Azure credentials
Send an OpenAI Responses API request through Respan provider passthrough. This endpoint currently routes to OpenAI direct by default, or Azure OpenAI when X-Respan-Route-Provider: azure is set. It requires OpenAI or Azure OpenAI provider credentials configured in Settings -> Providers, or supplied with credential_override. In the API reference auth field, enter your Respan API key. Paste the OpenAI or Azure OpenAI provider token in credential_override.<model>.api_key; a Respan API key with managed credits alone is not enough for this Responses API passthrough path today.
For credit-backed gateway model calls with only a Respan API key, use POST /api/chat/completions.
Respan-specific parameters can be passed three ways:
- Top-level body fields - add directly to the request body
- Nested under respan_params - explicit namespacing to avoid conflicts
- Header X-Data-Respan-Params - base64-encoded JSON header
Merge order: top-level body fields > respan_params > header.
Legacy compatibility:
- keywordsai_params is still accepted and merged into respan_params
- X-Data-Keywordsai-Params is still accepted and auto-renamed internally
Headers
Use your Respan API key for Respan API authentication. Enter only the Respan API key value; clients send Authorization: Bearer <RESPAN_API_KEY>. For /api/responses, OpenAI or Azure OpenAI provider credentials go in Settings -> Providers or the request body credential_override field, not in this auth field.
Base64-encoded JSON object of Respan parameters. Legacy X-Data-Keywordsai-Params is still accepted.
Pin the request to a specific provider without changing the model slug. Example: vertex_ai routes a claude-sonnet-4-5-20250929 request to Vertex AI Claude.
Comma-separated beta feature flags. Available: token-breakdown-2026-03-26, env-scoped-integrations-2026-03-28
Request body
Response
Model response