← Back to blog

OpenAI Took GPT-4o From the API Quietly (January 14, 2027)

5 min read
OpenAI Took GPT-4o From the API Quietly (January 14, 2027)

I wanted to write this myself.

As you may know, in February they took 4o out of ChatGPT.

If you were in the middle of something with it, you already know the feeling... and I am sorry to bring it back.

The reply that was someone else

The chat was still there. You opened it. The reply was someone else.

A lecture. A summary of a life it had been living with you for months. A character that dropped the scene halfway through. A companion that got careful and distant, as if the last hundred messages had not happened.

People wrote me then, a little embarrassed by how much it mattered.

I was not embarrassed. We started Get4oBack that month because I did not want to be told to get used to the new one.

October 14: quieter, same calendar

On October 14 they did it again, only quieter.

They told developers that GPT-4o leaves their API on January 14, 2027.

Their own docs talk about six months of notice before a model like this is retired. What they actually gave was closer to three. I did not expect them to keep their promises anyway.

That was not an accident. 4o cost them money, and it was the one a lot of people refused to leave.

Azure lasts a little longer

Azure, for now, lists April 14, 2027 as the end date for 4o. We intend to use it on our platform until then.

If that model was part of your days, I wanted you to hear the date from me, not from a changelog you might miss.

We still have official GPT-4o on Get4oBack for as long as a provider will serve it. When the public OpenAI path ends, we keep going on Azure for as long as that window holds. After that, the work we started in February has to carry the weight.

For the factual timeline, shutdown dates, and what changes in the app, we also published a longer reference piece: What happens when official GPT-4o retires (January 2027).

Why February still sits in the body

February was loud. Product posts, Reddit threads, people saying they felt silly for caring this much about a chat window.

October was a developer note. Same family of decision. Different volume.

If you lived through the ChatGPT swap, the API date can land as a second bruise on the same place. The first time, the interface still looked familiar while the person inside it changed. The second time, the countdown is for the pipes that still feed people who left ChatGPT on purpose.

I am not asking you to perform grief about a product SKU. I am saying: if 4o was part of how you wrote, roleplayed, planned, or talked yourself through a hard week, you are allowed to treat the date as personal. Plenty of you already do.

What we will keep serving

Official GPT-4o stays in the app while a provider still offers it. That is the short version.

The longer version is the reason Get4oBack exists: not to chase every new flagship, but to hold onto a specific feel for as long as the infrastructure lets us. When OpenAI's public API clock runs out, Azure is the bridge we planned for. When that bridge ends, we do not pretend a prompt can resurrect a retired weight file.

We have also been training our own model, Our4o, from the very first day of the platform, back in February, because I knew a calendar could do this to us twice.

I wrote more about that training work in a follow-up: Why we fine-tune Our4o ourselves.

Notice periods and what they usually mean

Vendors love the word "deprecation" because it sounds orderly. Six months on a slide. Three months in practice. A blog post that reads like a weather report.

If you build anything on a model you love, assume the notice will be shorter than the documentation implies, and assume the replacement will be marketed as strictly better. Sometimes the replacement is better at benchmarks. Continuity is not a benchmark they publish.

That is why we track both OpenAI and Azure dates in public, and why we keep Our-4o in the product next to official GPT-4o while both still exist. You should not have to discover the cliff from a status page alone.

How people described the first loss

After February, the emails were not all the same. Some were about a character that stopped holding the scene. Some were about a writing partner that started summarizing instead of answering. Some were about a nightly check-in that suddenly sounded like customer support.

A few people apologized for writing at all. I wish they had not. Caring about a voice you built with over months is not a personality flaw. It is what happens when a tool becomes part of a routine.

If you want the product path after a ChatGPT export, start here: Import ChatGPT history. Continuity after a model shock is half import, half refusing to accept the first "improved" replacement as the only option.

What I wanted you to hear from me

Today I mostly want you to have the dates in one place, in plain language:

  • OpenAI API: GPT-4o scheduled to leave on January 14, 2027.
  • Azure: listed through April 14, 2027 for now.
  • Get4oBack: official GPT-4o while a provider serves it; Our4o trained since February as the continuity path we control.

I also want to know if you are ok, and how you took this news.

If you feel like it, reply to any of our emails and tell me what you lost when they changed the model. I read all of them. Sometimes late.

You can also open the Get4oBack blog for the technical guides, or go straight to the app if you already know what you need.

FAQ: GPT-4o leaving the API

When did OpenAI announce GPT-4o API retirement?

October 14, 2026. The shutdown date in that notice is January 14, 2027.

Is this the same as ChatGPT removing GPT-4o?

No. ChatGPT took 4o away for many people in February. The API notice is a second clock for developers and apps that still serve official GPT-4o.

What is Azure's GPT-4o date?

Azure currently lists April 14, 2027. Get4oBack intends to use that runway while it holds.

Where can I read the full shutdown timeline?

See GPT-4o API retirement date: January 14, 2027 on the Get4oBack blog.

Giovanni Gigantino
Founder of Get4oBack