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
400 error when getting collection view #11
Comments
Smoke Test also eventually fails:
|
It's because of the error present in the console? The error shows up when notion's database is opened. frame.1bee5518.js:1 POST https://api-iam.intercom.io/messenger/web/events 429 |
That looks unrelated. It's some CORS issue with intercom that existed previously. |
I am getting the same error, I'm assuming the API changed. |
running into the same issue as well |
getting same error. It worked well until three days ago. |
Same issue. |
Looking at the log, it looks like the post data structure might have changed? This is an input 400 error so it's client side. Query is set to an empty string; perhaps the API now requires a query? Or the token nomenclature could have changed. I lack the time ATM to look deeper but if someone could re-run the API calls to see if anything changed, they could use this blog post as a guide.
|
Change from "searchPagesWithParent" to "queryCollection" which requires at least JSON data "collectionId", "collectionViewId" and "loader" now. I try to send a post request to the /api/v3/queryCollection which returns a similar output as before data structure. |
For me I simply save the "collectionViewId" into the "NotionClient" class and and hard-code the "loader" part for the "queryCollection" JSON data. Because the main goal for me is to get all the blocks inside the table and I did some modifications which works for me. Waiting for the update too! |
My version currently has a fix. I couldn't find any example of "searchPagesWithParent" in my network logs while trying various things. In the javascript source I did find something like this: (If you view my commits, I also had a solution ready that avoided |
@evertheylen Using your repo and things are working normally again. Thanks. |
Working great, thanks! |
@evertheylen Search doesn't work now, although it may never have, but it could be related.
Error:
|
Note users facing this issue can temporarily use code in #10 while it is merged.
|
I also had this same error when trying to run this on library on a database page. +1 for the fix from For anyone using pipenv, just install using their repo instead (took me an hour to figure this out since I am just getting started with pipenv, so figured I'd share here):
|
Thanks for all the great sleuthing and fixing! Sorry for the delay on my side (I'm the Executive Director of a nonprofit that's using Notion a lot, so I'm committed to keeping this library maintained, but things can get... busy). 😺 @evertheylen's lovely PR #10 was merged a couple of weeks ago and should be live on PyPI in 0.0.20 -- please re-open if you're still seeing issues. Thanks! |
Tracceback is below. Quick start instructions worked fine on a page, but when trying to pick up a database/collection I get the following. Any suggestions, and thanks!
The text was updated successfully, but these errors were encountered: