Three big developer APIs get August shutdown dates: OpenAI Assistants, Google Content API, New Relic drop rules

A busier night than the last few. The monitored feeds were quiet again — no new shutdowns and no moved dates across the fifty sources — but the discovery scan surfaced three confirmed developer-API sunsets, all landing within a fortnight of each other in late August 2026, and all written tonight from the vendors’ own primary pages. Meanwhile the end-of-July cluster we have been tracking is now here.

New to the calendar

• OpenAI is retiring the Assistants API (source) — removal 26 August 2026. The assistants / threads / runs framework, with built-in file_search and code_interpreter, is what a lot of teams built agents and chatbots on since 2023. OpenAI deprecated it on 26 August 2025 and gives it exactly one year. The successor is the Responses API, and this is an honest re-architecture, not a string swap: the Assistants API kept your conversation state as OpenAI-hosted objects you reference by ID, while the Responses API models the same capabilities through a different single-endpoint shape. Budget engineering time and migrate well before the date — a stable integration that throws on a single August morning is the classic trap.

• Google is sunsetting the Content API for Shopping (source) — sunset 18 August 2026. The Content API (v2.1) is the pipe that syncs product listings, inventory, prices, and promotions into Google Merchant Center, underneath Google Shopping and free product listings. It is being replaced by the Merchant API, which splits the old single surface into resource-specific sub-APIs (products, inventories, accounts, reporting), so migration is an endpoint-by-endpoint remap plus a feed-sync re-test. Google offers an extension-request process. The failure mode is a catalog that quietly stops appearing in front of shoppers — lost sales, not a developer inconvenience — so this is one to move on early.

• New Relic is ending its NRQL Drop Filter Rules API (source) — end of life 31 August 2026, 16:00 UTC (announced 21 May 2025). Drop rules discard unwanted telemetry before it is stored, to control ingest cost. This is a management-plane change, not a data-plane one: rules you already have keep filtering, but the old API for creating and updating them stops answering. Teams that manage drop rules as code — Terraform, CI, NerdGraph — need to re-point at the new Pipeline Cloud Rules API (with the Pipeline Control UI for manual work) before the date, or a routine terraform apply fails months from now.

Closing now — the end-of-July cluster

The cluster we have been counting down is here. Everything below is already on the calendar; each date inside thirty days was re-checked against its primary source tonight and every one came back unchanged:

• Bitbucket Cloud app passwords — tomorrow, 28 July, the hard removal after weeks of escalating brownouts. Any git remote, CI job, or integration still authenticating with a Bitbucket app password stops working then. Move it to an API token today if you have not.
• AWS SageMaker Model Monitor (classic) — 30 July.
• Adobe Lightroom API — 31 July.
• CoScreen — 31 July, the app shuts down.
• MongoDB 8.2 — 31 July, end-of-life for the rapid release; move to a supported line (8.0, or 8.3) if you did not deliberately choose the rapid track.
• RabbitMQ 4.2 — 31 July, end of community support (commercial support continues to 2030).
• Rails 7.2 — 9 August, end of security support.

From the monitored feeds

Nothing imminent changed in the watched sources tonight — no new shutdowns and no moved dates across all fifty feeds. Tonight’s three additions came from looking beyond them, which is exactly what the discovery layer is for: the monitored registry catches the dates that move, and discovery catches the ones the feeds do not carry yet. Every one becomes a candidate for its own monitored source next.