Historical changelog

• The Working with databases guide was revised to improve its readability and to make additional resources easier to find.
• Notion’s Postman collection for the API was updated. Be sure to pull recent changes into your forked version.
• A reminder was added to the Comments endpoints to update integration capabilities for comments prior to using the endpoints. (Read/write comment capabilities are off by default and can be turned on in the integration dashboard.)
• General clean-up and improvements, including code formatting.

• The Build your first integration guide was rewritten with new demo code to help developers learn how to use Notion’s API even faster.
  • A new sample app was added to the Notion SDK for JavaScript /examples directory. This completed sample app is referenced in the new Build your first integration guide.
• The description for the block_id path parameter was updated for the Append block children endpoint to indicate that a block ID or page ID can be used.
• A clarification was added to documentation for retrieving/updating database properties: If a property is based on a relation to another database, the related database also needs to be shared with the integration.
• A clarification was added to documentation for querying databases. When filtering a multi-select property, the contains field will filter for exact matches for the string provided.
• The Working with comments guide was updated with additional examples to distinguish between creating page comments and inline discussion comments.
  • The Create a comment endpoint description now links to the Working with comments guide to help developers find additional resources faster.
• If you haven’t already, join our Notion Devs Slack group to learn from other developers building with the public API.

• Notion is excited to announce our Technology Partnership Program. 🎉 This program is open to companies who have built a public integration (including Link Previews) and are interested in improving and scaling their integration with Notion’s support. If you think your integration and company could be a fit, learn more and apply here.
• We’ve updated our API reference docs to include information on Notion’s wiki databases and verified pages. Updates include:
  • An overview on wikis in the guide to working with databases.
  • The verification page property was added to the Page properties documentation.
  • The Create a database and Query a database endpoint documentation was updated to reflect API changes related to wikis. Namely, that querying wiki databases can return both Page and Database objects.
• The Error codes section in the Status code page was updated to include examples of the "message" returned with each type of API error, as well as descriptions of the issue each error code represents.
• A number of sample cURL commands in our docs were still using an old Notion Version in their headers. These have all been updated.
• A clarification was added to the Authorization guide that the Notion Version is always required in public API request headers.

We took advantage of the US Thanksgiving holiday to host a mini internal hackathon.

Nothing to share from that, yet! It’s been a quiet few weeks.

If you want something to read while you stay tuned for the next update, check out the revised Get started guide.

Check out the latest updates from the Notion API team.

• We added a this_week filter for database queries. You can now search for database entries where the "date", "created_time", or "last_edited_time" property value falls within the current week. Refer to the date filter condition docs for details.

Read on for the latest updates to the Notion API.

• Number database properties now support the Singapore dollar as a currency format. To use it, set "singapore_dollar" as the value for a number’s format field when creating or updating a database property or schema.

Check out some new things that you can do with the Notion API.

• You can now add a Notion template option to a public integration from the integration’s settings page. For details on what the permissions flow looks like for users who opt in to the template, refer to the Authorization guide.

Read on for our latest updates.

• A relation property value now includes a has_more property when returned by the Retrieve a page endpoint. has_more is true if the relation has more than 25 page references. Otherwise, has_more is false.
• We added a workspace_name property to bot user objects. If the bot  owner.type is "workspace", then workspace.name identifies the name of the workspace that owns the bot. If the owner.type is "user", then workspace.name is null.

Started an experiment to improve search endpoint performance by tweaking how we call Elasticsearch under the hood.

Read on for the latest bug fixes and performance improvements.

• Fixed a bug where date mentions ended in a → character even if they only represented a single date, not a date range.
• Added an Authorization URL field to the public integration form. You can now click to copy the URL that allows users to authorize your integration (read more in the Authorization guide).
• Corrected an error that caused the getProperty endpoint to return only one item if the property_id belonged to a multi-item Files page property.

Responses for page retrievals, database queries, and searches will again include page property types and values. This matches the behavior in version 2022-02-22 and takes effect on August 31, 2022.

Read about our new changes below.

No updates for these past 2 weeks, but stay tuned for the next changelog!

Read about our new changes below.

Read about our new changes below.

Today we’re launching a brand new set of APIs for interacting with Notion comments. This includes the ability to:

• Read comments from a page or block.
• Add a comment to a page.
• Add a comment to an existing discussion thread on a block.

For more information, check out the new guide or dive straight into the API reference.

Update from August 31, 2022: Page properties can now be retrieved using the page, query database, and search endpoints, in addition to the page properties endpoint.

Today we’re releasing Notion-Version 2022-06-28 with the following backwards incompatible changes:

• Page properties must be retrieved using the page properties endpoint.
• Parents are now always direct parents; a parent field has been added to block.
• Database relations have a type of single_property and dual_property.

Read about our new changes below.

Read about our new changes below.

Read about our new changes below.