Skip to content
New issue

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

Add new API endpoints #5

Open
dragonman225 opened this issue Jun 20, 2020 · 1 comment
Open

Add new API endpoints #5

dragonman225 opened this issue Jun 20, 2020 · 1 comment
Assignees

Comments

@dragonman225
Copy link
Owner

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

{
  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.

@dragonman225 dragonman225 changed the title Add a new API endpoint "syncRecordValues" Notes about new API endpoints Sep 6, 2020
@dragonman225 dragonman225 changed the title Notes about new API endpoints Add new API endpoints Sep 6, 2020
@dragonman225
Copy link
Owner Author

A new and interesting one, /api/v3/getBacklinksForBlock.

Request body

{"blockId":"1c4d63a8-ffc7-47be-a565-8672797a595a"}

Response body

{
  backlinks: [],
  recordMap: {}
}
  • The recordMap is the familiar one like this.

@dragonman225 dragonman225 self-assigned this Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant