Mathi.
← All work

Client work

Assistants → Responses API Migration

Led the upgrade of a bid management platform’s AI services from OpenAI’s Assistants API to the Responses API.

OpenAI Responses APIOpenAI Assistants API

The problem

The platform’s AI features were built on the Assistants API, which means managing threads, runs and polling as server-side state. OpenAI has deprecated the Assistants API in favour of the Responses API, so the features had to move to stay supported.

My role

Lead: planned the upgrade, set the approach for the team, reviewed the work and owned the release.

How it works

  1. 01BeforeCreate a thread, add messages, start a run, poll until it finishes
  2. 02UpgradeRewrite each AI call as a single Responses API request
  3. 03TestCheck the AI features still behave correctly before release
  4. 04AfterOne request in, one response out — no polling loop

Key decisions

Stateless over stateful

Dropping the thread-and-run polling loop removed a whole class of “stuck run” states, and the code that existed only to manage them.

Move before the deadline, not at it

Upgrading while the old API still worked meant the team could test calmly and ship it as a normal release, instead of a rushed fix when the API is switched off.

Outcome