Notion API updates, May 2026: what shipped and what it still cannot reach

The mid-May 2026 release, published on Notion's developer changelog and grouped under the platform's 3.5 release notes, has four headline items. First, a meeting notes query endpoint that returns AI meeting notes for the integration's user, with optional filter, sort, and limit parameters and normalized attendee aliases. Second, a 10,000-result pagination limit on data source and view query endpoints, with a new request_status field in the response that tells you when a query matched more rows than the cap. Third, multi-value filters: equals and does_not_equal on select and status properties, and contains and does_not_contain on multi_select properties, now accept an array of values instead of a single value. Fourth, agent-tool fixes: the search tool no longer drops Slack DMs and private channel results when the workspace has the Slack integration enabled, the fetch tool accepts any first-party Notion domain, and page resources from the fetch tool now carry an is_archived flag.

Before this release, a query endpoint that matched more rows than the engine would page through gave you no signal that the result set was truncated. You paged until has_more was false and assumed you had everything. With the 10,000-result cap, has_more going false no longer guarantees completeness, so the response now includes request_status. If your integration syncs a large database, you have to read request_status on every page and treat an incomplete status as a real branch in your code, not an edge case. The honest reading of this change is that very large Notion databases are no longer fully enumerable through a single query call, and you need filtering or a different access path for those.

No. The old approach was to build an or block with one condition per value, which still works. The May 2026 change lets equals, does_not_equal, contains, and does_not_contain take an array directly, which collapses a five-value or block into one condition. It matches the multi-value conditions the Notion UI already supported. It is a convenience and a payload-size win, not a breaking change, so existing or-block filters keep working and you can migrate at your own pace.

It returns AI meeting notes scoped to the integration's user, which means it depends on the integration's authorized user having access to those notes and on the workspace having the meeting notes feature. It is not a workspace-wide firehose. Treat it as a per-user read with filter, sort, and limit, and check the official changelog at developers.notion.com for the exact capability and scope requirements before you build against it.

Because the REST API is a deliberately bounded surface, not a mirror of the desktop client. As of mid-May 2026 it exposes pages, databases and data sources, blocks, users, comments, file uploads, search, and the newer agent and meeting-notes endpoints. It does not expose the editor's full block-level interaction model, view configuration changes, sidebar and workspace navigation, account and member settings, or the in-editor Notion AI surface. Anything that lives only in the UI has no endpoint, and no May 2026 update changed that. That gap is structural, which is why a desktop agent that drives the real app is a different tool from an API client, not a worse one.

Fazm wraps Claude Code and Codex in a native macOS app, and the same agent loop reaches past the terminal. For Notion specifically it leans on the browser extension, because Notion's desktop app exposes a thin accessibility tree: the editor is a contenteditable surface and the macOS accessibility tree underdescribes block boundaries. So Fazm drives the real notion.so tab in your already-logged-in browser, the way a human would, with a screenshot fallback when the tree is not enough. That means it can do UI-only tasks the REST API has no endpoint for, and it does not need an integration token or OAuth setup for personal automation. The tradeoff is honest: an API call is faster and more reliable than driving a UI when an endpoint exists, so Fazm is the right tool for the gap, not a replacement for the API where the API already works.

Notion publishes it at developers.notion.com on the changelog page. The notion.com releases pages cover the broader product, including the 3.5 developer platform release notes. For the official JavaScript SDK, the makenotion/notion-sdk-js releases page on GitHub tracks which API changes have landed in a published client version. This page is a snapshot dated 2026-05-18; for anything time-sensitive, the developer changelog is the source of truth.