> ## Documentation Index
> Fetch the complete documentation index at: https://docs-vip.apigo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenAI Responses API example

> Unified Responses API example for OpenAI-style integrations.

## Recommended endpoint

* [OpenAI /v1/responses](/en/api-reference/endpoints/openai/responses)

## Minimal request

```json theme={null}
{
  "model": "gpt-4.1",
  "input": "Summarize the core value of ApiGo in 3 bullet points."
}
```

## cURL example

```bash theme={null}
curl https://api-vip.apigo.ai/v1/responses \
  -H "Authorization: Bearer $YOUR API KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4.1",
    "input": "Summarize the core value of ApiGo in 3 bullet points."
  }'
```

## Python example

```python theme={null}
from openai import OpenAI

client = OpenAI(
    base_url="https://api-vip.apigo.ai/v1",
    api_key="<YOUR API KEY>",
)

response = client.responses.create(
    model="gpt-4.1",
    input="Summarize the core value of ApiGo in 3 bullet points.",
)

print(response.output_text)
```

## Node.js example

```js theme={null}
import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://api-vip.apigo.ai/v1",
  apiKey: process.env.YOUR API KEY,
});

const response = await client.responses.create({
  model: "gpt-4.1",
  input: "Summarize the core value of ApiGo in 3 bullet points."
});

console.log(response.output_text);
```

## Best practices

* Prefer `responses` for new integrations that may grow into tools or multimodal input
* Reuse `previous_response_id` instead of resending the entire history every turn
* Build your parser around both `output_text` and `output[]`