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

NotionAPI collectionQuery error Response code 400 (Bad Request) #127

Closed
galacoder opened this issue Sep 2, 2021 · 9 comments
Closed

NotionAPI collectionQuery error Response code 400 (Bad Request) #127

galacoder opened this issue Sep 2, 2021 · 9 comments

Comments

@galacoder
Copy link

Hi there,

I got a very frustrated issue and I really need your help!

I have been using nextjs-notion-starter-kit for since June and lately I can't access all the pages I recenly created. After many hours of looking for the issues, I found out that I can open those pages via localhost, but not on vercel.

Then, I tried to redeploy but hit the NotionAPI collectionQuery error Response code 400 (Bad Request) (plz find the attachment) .
Screen Shot 2021-09-02 at 22 28 16.

I was about to give up. Then, I decided to try one last shot with just using the examples from react-notion-x. I deployed to vercel without a hinch! it worked somehow.

Then, I tried to update the following packages in nextjs-notion-starter-kit as follows:

  • "node-fetch": "^2.6.1",
  • "notion-client": "^4.8.6",
  • "notion-types": "^4.8.2",
  • "notion-utils": "^4.8.6",

But nextjs-notion-starter-kit still hit NotionAPI collectionQuery error Response code 400 (Bad Request).

Anyone knows what happend? Plz advise!

Tks!

@ToulouseDataViz
Copy link

Hello,

Same thing, a perfectly well functionning website suddendly stop working with NotionAPI collectionQuery error Response code 400 (Bad Request).
Is there a change in Notion that causes this error ? Do you plan to correct ?

Cheers

Alain

@shyjal
Copy link

shyjal commented Oct 6, 2021

Notion is notorious for making unannounced breaking changes to its API. They are doing it for the APIs that are versioned and are live for a long time. Seems like unprofessional behaviour from such a big company.

@transitive-bullshit
Copy link
Member

This looks like a breaking change from notion's private API. I believe @normdoow is looking into it; otherwise I'll try to fix it in the next few days.

Thanks for the report @onlineworld69 💪

@ToulouseDataViz
Copy link

"notion-client": "^4.9.3",
"notion-types": "^4.8.2",
"notion-utils": "^4.8.6",

Seems to fix the problem for me
Thanks you @normdoow
Alain

@normdoow
Copy link
Collaborator

normdoow commented Oct 6, 2021

Yep, should be fixed in notion-client v4.9.3. Though board views have not been fixed yet. More changes are required to get it working there.

@aleksanderpalamar
Copy link

I'm having the same problem with my application on the console, the NotionAPI error is appearing collectionQuery error Response code 400 (Bad Request) and with that it's not rendering the Notion content on my blog, does anyone have any solution to fix this proble
error
m?

@normdoow
Copy link
Collaborator

normdoow commented Oct 7, 2021

@aleksanderpalamar if you are using https://github.com/transitive-bullshit/nextjs-notion-starter-kit you'll need to update the notion-client version that you are using. It doesn't look like it has been updated there.

@Pipe-Runner
Copy link

Yep, should be fixed in notion-client v4.9.3. Though board views have not been fixed yet. More changes are required to get it working there.

Thankyou for fixing it <3

@normdoow
Copy link
Collaborator

This is fixed in notion-client v4.9.3. Seems like it is working for most people.

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

7 participants