Implement the new data source and database endpoints

[ramnes]

Notion is planning a major API update for API version 2025-09-03: makenotion/notion-sdk-js#600

Let's replicate their work here.

[FlorianWilhelm]

🙈 It seems there always a change with the Notion API. As far as I understand it only concerns database calls and is detailed here. I won't be able to work on it but maybe it helps someone :-) I'll definitely use it in Ultimate Notion when it is implemented here.

[ramnes]

Notion published this migration documentation page, which may be worth reading before working on this: https://developers.notion.com/docs/upgrade-guide-2025-09-03

[ramnes]

Responses now have an additional_data field for data sources: makenotion/notion-sdk-js#603

[sashanclrp]

In what status is this?
Which branch should I clone to help you guys have this upgrade of the new Notion Database/Datasources API finished by the end of the week?

Please let me know!

[FlorianWilhelm]

@sashanclrp as far as I know, no one has started to work on it.

[jralduaveuthey]

May i ask what is the status of this?
Is it expected that my automations will stop working?
Is there a migration guide or similar?

Our usage of notion-client:
We heavily rely on this library across our infrastructure with the following core functionality:

• Client(auth=token) initialization
• databases.query() with pagination, complex filters (date/select/text/relation/compound), and sorting
• databases.retrieve() and databases.update()
• pages.create(), pages.update(), pages.retrieve() with various property types (title, rich_text, select, date, checkbox, url, email, relation, etc.)
• comments.create()
• blocks.children.list(), blocks.retrieve(), blocks.append_children()

We use pagination extensively via has_more/next_cursor and handle all standard Notion property types. Any breaking changes to these methods would significantly impact our production systems.

We use notion-client==2.4.0.

Thank you!

[FlorianWilhelm]

@jralduaveuthey, this is an OSS project, which is free to use and @ramnes works on it in his spare time (to the best of my knowledge). You didn't even take the time to read the migration guide of Notion itself, which would have answered most of your questions, nor did you read this thread carefully, in which case you would have seen that @tsinglinrain is working on it and it will be released whenever the solution of @tsinglinrain satisfies the high standards of @ramnes. This is how successful OSS projects work, so please be a little bit nicer. Your post conveys the attitude of a ticket you would post to some software company for whose software you are paying.

There is always the option to speed things up by sponsoring the maintainer or providing a bounty for a feature :-)

[jralduaveuthey]

@FlorianWilhelm You're absolutely right, and I apologize for the tone. Don't take my message too seriously - it was mostly Claude-generated with some context notes for my future reference.

I have huge respect for OSS maintainers and the work you do in your spare time. Thanks for the great work on this project!