Notion Developers Updates & Release Notes

unsupported formula and rollup property values

The API can now return formula and rollup page property values and property item values with type set to "unsupported" and an empty unsupported object. This happens when a value depends on too many related pages or nested formulas and rollups. The response doesn't include a partial value. Treat the property as unavailable. Rollups still include the function field. To make the value available, reduce the number of related pages or simplify the nested formulas and rollups.

JavaScript SDK 5.24.0

We released @notionhq/client v5.24.0. It adds client.blocks.meetingNotes.create() for creating a meeting note, typed unsupported formula and rollup values, and APIErrorCode.InvalidBeta for handling invalid_beta responses.

Clearer per-tool access status

The current_tool_access status previously called limited_free_trial is now available_with_limit. The new name makes clear that a tool is available until the usage limit included with the workspace's plan is reached. This is a naming and description update only; it does not change tool availability or usage limits.

Fetch documentation resources with the fetch tool

The Notion MCP fetch tool now accepts notion://docs/* URIs (for example, notion://docs/enhanced-markdown-spec) and returns the same content as the MCP resource of the same URI. This gives MCP clients that cannot read MCP resources a way to load the specs referenced in tool descriptions.

Per-tool access map in notion-fetch self

The notion-fetch MCP tool's self response now includes a current_tool_access map, so clients can tell before making a call which tools will actually run on the connected workspace's plan and which would only return an upgrade prompt. Each entry's status is available, limited_free_trial (calls succeed via a free or metered trial allowance), upgrade_required (the entry also carries an upgrade_url into the workspace's upgrade flow), or not_enabled. See Integrating your own MCP client.

New identity fields in OAuth token responses

User objects now include an email_verified boolean next to person.email, indicating whether Notion has verified that email address. The field appears anywhere person emails do, including the owner in OAuth token responses and List all users results.

Notion MCP token responses now include top-level user_id, workspace_id, and email_domain fields on successful authorization-code exchanges, so MCP clients can associate a connection with a Notion user and workspace without an extra call. See Integrating your own MCP client.

New response fields like these are backwards-compatible additions and appear on every API version. Parse responses leniently: ignore fields you don't recognize rather than rejecting them.

Notion app links in API responses use the new app domain …

We released v5.23.0 of @notionhq/client, our SDK for JavaScript and TypeScript. Here's what's new:

Verify webhook signatures with one call

The new verifyWebhookSignature() helper confirms that a webhook event really came from Notion, so you no longer need to hand-write the HMAC check. Pass the raw request body, the X-Notion-Signature header, and your subscription's verification_token; the helper compares signatures in constant time and returns false instead of throwing on malformed input. It works without configuration in Node.js 18+, Bun, Deno, Cloudflare Workers, Vercel Edge Functions, and browsers. A companion signWebhookPayload() generates signatures for testing your handler.

Read every row in a large data source

A single data source query returns at most 10,000 results, so plain pagination can silently miss rows. The new iterateAllDataSourceRows() and collectAllDataSourceRows() helpers page past the limit using the windowing approach from the Query large data sources guide, de-duplicating rows along the way. Stream rows with the iterator, or collect them into an array when the full result fits in memory.

Start and poll async page writes …