By Nineteen days. That’s how long developers who built against Notion’s private alpha agent API have before their integrations stop working. Notion’s alpha routes for threads, messages, and chat go dark on September 30, 2026 — no extensions, no grace period. The replacement is in public beta and has been for months. If you haven’t moved yet, now is the time.
What Breaks on October 1
Any code calling Notion’s private alpha agent endpoints — /agents, /threads, /messages, or /chat — returns errors starting October 1. These routes were invite-only, available during the pre-May 2026 alpha period when Notion’s developer platform was still in closed testing.
The blast radius is wider than it sounds. Slack bots that surface Notion agents, internal dashboards querying agent threads, n8n or Zapier flows built on the alpha, mobile clients streaming responses — all of these are on the chopping block. The standard Notion API for pages, databases, and blocks is not affected. This is specifically about the agent layer.
The Replacement: Sessions and Events
The public beta API replaces the old threads-and-messages model with sessions and events. The structural change is simple: old routes used query parameters; new routes use JSON request bodies. Old routes returned threads and messages; new routes return sessions and events. If you find-and-replace the data model in your integration, you’re most of the way there.
The new model is meaningfully better. You can now stream an agent’s reply in real time instead of polling. You can submit actions mid-session — useful for confirmations and approval flows. And you can page through a session’s full event history for debugging and audit trails. Agent management is also now programmatic: use the Query agents endpoint to list agents a token can reach, pull per-agent usage via Retrieve agent insights, and set credit limits or enable/disable agents in bulk via an async batch operation. Notion’s developer platform announcement covers the full vision behind these APIs.
Notion Workers: The Platform Behind the API
The migration deadline is the urgent news, but the bigger story is what Notion has built around it. Notion Workers, launched in May 2026, are a hosted TypeScript runtime: you write the code (or have your AI coding agent write it), deploy with ntn workers deploy, and it runs in Notion’s secure sandbox. No server to manage, no Docker container, no Cloudflare account.
Workers shifted to paid status on August 11, 2026, running on Notion credits at $10 per 1,000 units, shared across a workspace and reset monthly. Deploying Workers requires a Business or Enterprise plan. The CLI itself is available on all plans.
One million agents have been built on Notion since the February 2026 Custom Agents launch. That number contextualizes why the September 30 shutdown is a real event, not an administrative footnote — there are integrations in production that need to move.
MCP Users: What Changed This Month
If you use Notion through an MCP server, the September 2026 changelog added session tools directly to the MCP layer. You can now query and search agent sessions, start a session, send follow-up messages, check status, stop a run, and list session events — all from your MCP client without dropping to raw HTTP. The notion-fetch tool also now accepts view:// URLs so you can read saved database view settings directly. Error handling is improved too: instead of a generic permission error when a workspace lacks Notion AI access, the tools now return a recovery link. The official Notion MCP server on GitHub is updated to include all of these changes.
Three Steps to Take Right Now
If you’re affected, the path forward is straightforward:
- Audit your integration. Search your codebase for calls to
/threads,/messages,/chat, or the old/agentsalpha routes. Any hit is a migration target. - Read the upgrade guide. Notion’s developer changelog includes the upgrading-to-public-beta section with before/after examples of the route changes.
- Test before September 28. Don’t wait until the last day. Give yourself a buffer to catch edge cases — especially around streaming and event pagination, which behave differently from the old polling model.
The sessions API is a real improvement. Streaming, programmatic management, and proper event history make it a more capable surface than what the alpha offered. Notion should have given developers more than a few weeks’ visible warning, but the platform itself is moving in the right direction. Just don’t let the upgrade happen by accident on October 1.
