We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems that Notion is using the new API endpoint /api/v3/syncRecordValues to get data instead of the old one /api/v3/getRecordValues.
/api/v3/syncRecordValues
/api/v3/getRecordValues
The new API looks like below:
Request body
{ recordVersionMap: { "<table_name>": { // e.g. block "<id>": "<version>" // <version> = -1 means the latest } } }
Response body
{ recordMap: { "<table_name>": { "<id>": data } } }
Does this change indicate that /api/v3/getRecordValues will be deprecated? We'll see.
The text was updated successfully, but these errors were encountered:
A new and interesting one, /api/v3/getBacklinksForBlock.
/api/v3/getBacklinksForBlock
{"blockId":"1c4d63a8-ffc7-47be-a565-8672797a595a"}
{ backlinks: [], recordMap: {} }
recordMap
Sorry, something went wrong.
dragonman225
No branches or pull requests
It seems that Notion is using the new API endpoint
/api/v3/syncRecordValues
to get data instead of the old one/api/v3/getRecordValues
.The new API looks like below:
Request body
Response body
Does this change indicate that
/api/v3/getRecordValues
will be deprecated? We'll see.The text was updated successfully, but these errors were encountered: