Skip to main content
Eden AI supports the OpenAI Responses API — a stateful alternative to chat completions that stores conversation history server-side, so you don’t need to resend the full message history on each turn.

Overview

Endpoints:
Provider-Dependent Behavior — The Responses API is a passthrough to the underlying provider. Stateful features (server-side storage, response retrieval/deletion, and previous_response_id chaining) are only available when the provider natively supports the Responses API (e.g. OpenAI). For all other providers, responses are not stored and the retrieve/delete endpoints are not functional.

How It Differs from Chat Completions

Create a Response

Request Parameters

Response Object

Top-Level Fields

output[] Item Types

usage Fields

Multi-Turn Conversations

Because responses are stored server-side, you only need to send the new user message and reference the prior response ID:
previous_response_id chaining only works for providers with native Responses API support. For other providers, responses are not stored server-side — you must manage conversation history client-side (e.g. by resending the full message array, as with chat completions).
Pass store: false if you don’t need persistence and want to keep the conversation stateless, like chat completions.

Retrieve a Response

This endpoint only works for providers with native Responses API support. For other providers, responses are not stored and this endpoint will return an error.
Fetch a previously stored response by ID:

Delete a Response

This endpoint only works for providers with native Responses API support. For other providers, responses are not stored and this endpoint will return an error.
Remove a stored response. The response will no longer be retrievable or usable as a previous_response_id:

OpenAI SDK

Use Eden AI’s Responses endpoint directly with the OpenAI Python SDK:
For multi-turn with the SDK:

Streaming

Set stream: true to receive output incrementally as Server-Sent Events. See Streaming for the full SSE format and parsing examples.

Next Steps

Chat Completions

Use the stateless chat completions endpoint

Streaming

Receive responses token by token via SSE

Structured Output

Constrain responses to a JSON schema