# Introducing the Responses API

**URL:** <https://community.openai.com/t/introducing-the-responses-api/1140929>\
**Category:** Announcements\
**Created:** [March 11, 2025, 10:17pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929 "2025-03-11T22:17:13Z")\
**Posts on this page:** 17\
**Page:** 2

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [March 20, 2025, 11:00pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/23 "2025-03-20T23:00:27Z")

</div>

Despite “continued support” stated, this sounds like Chat Completions deprecation to me, when new models can no longer be used…

 ![image](https://us1.discourse-cdn.com/openai1/original/4X/6/0/0/600c74e6cdde5a2108729eb83105b38afbc1c9ea.png)

---

<div class="post-metadata">

**Author:** ![kenji.prahyudi](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/kenji.prahyudi/32/567721_2.png) [@kenji.prahyudi](https://community.openai.com/u/kenji.prahyudi)\
**Post date:** [March 21, 2025, 2:55pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/24 "2025-03-21T14:55:06Z")

</div>

Is Response API available for all users yet? I can’t access it with my API key, though it has access to gpt-4o and gpt-4o-mini. It returns 403 forbidden “Project … does not have access to model gpt-4o-mini…”, even though with the same API key I can hit chat completion using the same models.

---

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [March 22, 2025, 1:39am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/25 "2025-03-22T01:39:17Z")

</div>

API keys can have allowed endpoints set on them.

You will note that there is no ‘/responses’ showing here in “Restricted” where you must enable individual endpoints:

 ![The image shows a settings interface for editing a secret key, with options to set permissions for different resources such as models and model capabilities. (Captioned by AI)](https://us1.discourse-cdn.com/openai1/original/4X/3/9/1/391cd9e54e8b9ca01aa2e9946b33977ddb85039d.png)

An “All” API key was immediately applicable to the Responses endpoint for me.

You may need to simply generate a new API key to be placed in your application for the endpoints behind “all” to be properly populated.

---

<div class="post-metadata">

**Author:** ![kenji.prahyudi](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/kenji.prahyudi/32/567721_2.png) [@kenji.prahyudi](https://community.openai.com/u/kenji.prahyudi)\
**Post date:** [March 22, 2025, 6:04am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/26 "2025-03-22T06:04:46Z")

</div>

Thanks for your reply! Yes I set the permission to “All”, but I can’t seem to hit the endpoint successfully. I’ll try your suggestion, if it’s not succeed I’ll start another thread. Thank you! 😄

---

<div class="post-metadata">

**Author:** ![damimax](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/damimax/32/339555_2.png) [@damimax](https://community.openai.com/u/damimax)\
**Post date:** [April 7, 2025, 1:26am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/27 "2025-04-07T01:26:31Z")

</div>

Any ETA for code interpreter for Responses API?

---

<div class="post-metadata">

**Author:** ![merefield](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/merefield/32/14812_2.png) [@merefield](https://community.openai.com/u/merefield)\
**Post date:** [April 17, 2025, 10:54am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/28 "2025-04-17T10:54:43Z")

</div>

Is there a Completions to Responses migration guide? I couldn’t find one … that would be useful.

However, in any case I’m not 100% a fan of switching unless Responses becomes an industry standard, because there are circumstances where you want to be able to support both OpenAI and third parties services, e.g. in generic open source repos.

Today I might want to use GPT 4.1, but tomorrow I might need to switch to Meta’s Llama 4 perhaps, something I can do with far less friction with Completions.

---

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [April 17, 2025, 11:10am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/29 "2025-04-17T11:10:51Z")

</div>

[https://platform.openai.com/docs/guides/responses-vs-chat-completions?api-mode=responses#compare-the-code](https://platform.openai.com/docs/guides/responses-vs-chat-completions?api-mode=responses#compare-the-code)

---

<div class="post-metadata">

**Author:** ![merefield](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/merefield/32/14812_2.png) [@merefield](https://community.openai.com/u/merefield)\
**Post date:** [April 17, 2025, 12:16pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/30 "2025-04-17T12:16:02Z")

</div>

Great find, thanks, very useful!

---

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [April 17, 2025, 12:41pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/31 "2025-04-17T12:41:07Z")

</div>

I understand about not wanting to switch and it’s hard to justify any reason. You get an internal iterator and response id storage for:

- server-side chat state: that can run a new model up to its 1M on chat with no management of the length;
- file search that has injected messages saying “user uploaded files”, destroying most use-case;
- web search that takes control and only produces a dump.
- reasoning “thinking” - then blocked without personal ID verification

…to then take away logprobs, logit\_bias, etc.

---

<div class="post-metadata">

**Author:** ![merefield](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/merefield/32/14812_2.png) [@merefield](https://community.openai.com/u/merefield)\
**Post date:** [April 17, 2025, 12:55pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/32 "2025-04-17T12:55:59Z")

</div>

I think the one benefit you get from the Responses API (if just doing single transaction “completions” and local tools) is reasoning summaries?

---

<div class="post-metadata">

**Author:** ![multitechvisions](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/multitechvisions/32/13977_2.png) [@multitechvisions](https://community.openai.com/u/multitechvisions)\
**Post date:** [April 17, 2025, 1:41pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/33 "2025-04-17T13:41:47Z")

</div>

This is the discussion I have been looking for, thank you all for your insights!💪

---

<div class="post-metadata">

**Author:** ![aprendendo.next](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/aprendendo.next/32/721758_2.png) [@aprendendo.next](https://community.openai.com/u/aprendendo.next)\
**Post date:** [April 18, 2025, 6:21pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/34 "2025-04-18T18:21:28Z")

</div>

They added a selector in the **right panel** for an equivalency of code for both versions in each [api docs](https://platform.openai.com/docs/guides/text?api-mode=responses):

 ![The image provides an overview of using the OpenAI API for text generation, featuring a code example with the Responses API and a dropdown menu showing different API options. (Captioned by AI)](https://us1.discourse-cdn.com/openai1/original/4X/8/2/1/8212a0e48f1d13be8839fcf25b10da8a125e2064.png)  
 ![The image shows a webpage titled "Images and vision" that describes vision capabilities for understanding images, including instructions for using URLs or Base64 encoded images. (Captioned by AI)](https://us1.discourse-cdn.com/openai1/original/4X/c/0/2/c0228468be686e921cb35b9ce2c069587ff2b99b.png)

---

<div class="post-metadata">

**Author:** ![ori.nachum](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ori.nachum/32/182695_2.png) [@ori.nachum](https://community.openai.com/u/ori.nachum)\
**Post date:** [May 4, 2025, 9:02pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/36 "2025-05-04T21:02:55Z")

</div>

Myself and my team are working on a middleware server.  
It lets you use Responses API (+features! We’re working on Web search, file search, etc.) but with any chat-completions compliant AI Provider.

It’s called “openai-responses-server” on GitHub (Can’t include links..)  
And we’re adding it as pypi package or docker image.

---

<div class="post-metadata">

**Author:** ![leo17](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/leo17/32/454605_2.png) [@leo17](https://community.openai.com/u/leo17)\
**Post date:** [May 15, 2025, 1:33am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/37 "2025-05-15T01:33:49Z")

</div>

> [@nikunj](#):
>
> **Feature parity between Responses and**  **Assistants** : We’re working on bringing key Assistants API features — like support for Assistant-like and Thread-like objects, plus the Code Interpreter tool — into the Responses API.

Any update on the timeline for Code interpreter? This is a key feature keeping us from switching to the Responses API

---

<div class="post-metadata">

**Author:** ![bragma](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/bragma/32/449492_2.png) [@bragma](https://community.openai.com/u/bragma)\
**Post date:** [May 19, 2025, 9:19am UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/38 "2025-05-19T09:19:18Z")

</div>

Hi, I am still waiting for “previous\_response\_id” (as a way to preserve conversation) to handle truncation of the chain based on message date/time , max number, or max tokens. With the release of models handling 1M tokens, this is even more important to control costs.

---

<div class="post-metadata">

**Author:** ![Gal\_Zanir](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/gal_zanir/32/667132_2.png) [@Gal\_Zanir](https://community.openai.com/u/Gal_Zanir)\
**Post date:** [August 16, 2025, 12:52pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/39 "2025-08-16T12:52:06Z")

</div>

Where’s GPT-5? Assistants API relying businesses need it in the Assistants API!

---

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [August 17, 2025, 12:42pm UTC](https://community.openai.com/t/introducing-the-responses-api/1140929/40 "2025-08-17T12:42:47Z")

</div>

> [@Gal\_Zanir](#):
>
> Assistants API relying businesses need it

Assistants endpoint users need to plan getting off Assistants before it is shut down. GPT-5 won’t be offered there.

[Previous page](https://community.openai.com/t/introducing-the-responses-api/1140929.md?page=1)
