Changelog

• Introduce Move page API to change the parent of an existing page.
• TS/JS example projects extracted to a new open-source project: notion-cookbook.
• Add support for customizing the position of a new page within the parent page.
• New APIs to power the flow described in our Creating pages from templates guide:
  • Introduce List data source templates endpoint.
  • Introduce template parameter to Create Page API.
  • Introduce template and erase_content parameters to Update Page API.

• Released notion-query-data-sources tool to Enterprise Notion workspaces with access to Notion AI.
• Tool consolidation: notion-get-user has been removed & its functionality has been rolled into notion-get-users.
• Fixed a bug causing child content to be deleted by the notion-update-page tool when using replace_content and replace_content_range modes.
• Removed Notion-flavored Markdown specification from notion-create-pages tool to conserve context tokens, since it exists behind a dedicated MCP Resource as well.

• Add support for is_locked boolean parameter on update page and database APIs (to update whether a page is locked in the Notion app UI)
• dataSource.update: add support for changing a data source’s parent database
• Remove page_id as a possible parent for CreateDataSourceBodyParameters
• Add request_id to Client log lines

​

📣 Important API update coming September 3rd

​

What you need to know:

• Current integrations continue working with single-source databases
• Update to the new API version to support multi-source databases
• We’re introducing the concept of API versioning to integration webhooks as well

​

What’s New?

• Revised Section 1.1 to refine the scope of application of the Developer Terms.
• Revised Section 3.1 to clarify prohibited uses of the API and created a new Section 3.2 for formatting purposes

​

What’s New?

​

Why the Change?

• Enhance compatibility with secret scanners and other security tools, making it easier to identify and manage Notion API tokens.
• Provide a clearer distinction between Notion API tokens and other types of secrets, reducing the risk of misconfiguration and improving overall security.

​

What Do You Need to Do?

• New Integrations: For any new integrations, the tokens will be automatically generated with the ntn_ prefix. Simply generate your tokens as usual through the Notion API settings page.
• Existing Tokens: All existing tokens with the secret_ prefix will continue to work without any changes. There is no immediate need to update your existing integrations.
• Token Format: We strongly advise against using regular expressions (regex) to identify or validate Notion Public API tokens. The token format may change over time, and relying on regex patterns could lead to false positives or negatives. Instead, treat the token as an opaque string and use it as provided.
• Best Practices: To handle Notion API tokens securely:
  • Store tokens securely using appropriate encryption methods.
  • Use Notion’s official SDKs or libraries when available, as they handle token management correctly.
  • Validate tokens by making authenticated requests to Notion’s API rather than parsing the token itself.

​

Questions or Concerns?

​

What’s New?

​

What’s New?

• Added: New property in_trash to indicate whether a page/block/database has been deleted or placed in “Trash”.
• Support: Both archived and in_trash properties are fully supported. Contact developer support for help during this transition or reach out in our Notion Devs Slack group.

​

What’s New?

• We added support for reading and writing names to file blocks in the public API. Read more here.
• We fixed the types in the SDK to support appending table and column blocks as children of toggle blocks.
• We updated the emoji and timezones available in the SDK.
• We added support for australian_dollar in the format field of number database properties.

​

What’s New?

• The Examples page was updated with all our most recent demo code. We’ve organized these sample integrations by level of experience with the Public API to help developers who are newer to the Public API find introductory code more easily.
• A note was added to all API endpoint documentation directing developers to review the Status codes page for a complete list of error codes that can be returned by API requests.
• A clarification was added to the Request limits page and Append block children endpoint documentation to indicate the current limit for appending a list of block children per API request. Up to 100 block children can be appended at a time.

​

What’s New?

• The updates related to the Formulas 2.0 launch are now live in the Public API. These changes will not impact most developers using the Public API; however, please note that the formatting of formula.expression, which is returned when retrieving a database with a Formula property, has changed. See Notion’s Help Center articles for more information on the Formula 2.0 changes:
  • Formulas 2.0: How to use Notion’s new and improved formulas with your existing setups
  • How to write Notion formulas that extend the capabilities of your databases
• The example for the Formula database property was updated to align with the new Formula 2.0 launch.
• New sample code was added to the Notion SDK for JavaScript’s examples directory. This new example demonstrates how to use the Public API with basic and intermediate levels of difficulty.