Versioning
The Notion API is versioned. Our API versions are named for the date the version is released. For example, our latest version is 2025-09-03.
Set the version by including a Notion-Version header. Setting this header is required.
A new API version is released when we introduce a backwards-incompatible change to the API. For example, changing a property type’s name.
In the above example, if you do not upgrade to the new version, you will continue to set text properties using text when creating or updating a page. Once you upgrade to the new version, you will need to use rich_text to set that same text property.
Similarly, the page response will be returned with the property type text on the old version, while on the new version, the response will say rich_text.
The Notion-Version header must be included in all REST API requests. This ensures the Notion API response is consistent with what your code expects.
The most recent Notion-Version is "2025-09-03".
For new features and additions to the API, such as adding a new API endpoint, or including a new object in an existing API endpoint’s response, there won’t be a new version. You’ll be able to take advantage of any new functionality on the version of the API you’re currently using.
Note: You may notice that Notion API URLs contain a v1. This is not related to the versioning described above. We don’t intend to change these URLs.