Getting object_not_found error with 404 response from Notion API

Other Questions Notion
1

I keep getting a 404 error with object_not_found message when trying to use the Notion API. I have already linked my database to my integration but it still doesn’t work.

I’m making the request through Postman and I’m confident that I’m using the right authorization token from my integration settings. The database shows as connected to my integration and my workspace is also properly linked.

I followed the official documentation step by step but I’m still running into this issue. What could be causing this problem? Am I missing something in my setup or is there an issue with how I’m formatting the request?

The error happens every time I try to access the database even though all the connections seem to be in place.

2

Check your request URL structure first. I had this exact issue - I was missing /v1/ in my endpoint path. Your URL should be: https://api.notion.com/v1/databases/your-database-id/query. Also, don’t use hyphens in the database ID. Notion shows them in the URL sometimes, but the API wants them stripped out. Make sure you’re sending the Authorization header as Bearer your_token, not just your_token. That object_not_found error is misleading - it usually means auth failed, not that the object’s actually missing.

3

Check your integration’s permission scope first. Your database might look connected, but you could have read-only access when you need query permissions. Go to your integration settings and make sure you’ve enabled database queries, not just basic read access. I’ve also run into issues with API versions - Notion’s really picky about this. Wrong versions throw object_not_found errors even when your auth is perfect. Make sure you’re sending JSON in your request body for database queries too. I wasted hours on this once because Postman was sending form data instead of JSON. The database looked connected but my request format was totally wrong.

4

Been there countless times. The 404 object_not_found usually means your database ID is wrong or you’re hitting the wrong endpoint.

Double check you’re using the actual database ID from the URL, not the database name. The ID is that long string of characters in your Notion page URL.

Make sure you’re hitting the right endpoint format: https://api.notion.com/v1/databases/{database_id}/query for querying.

Honestly, debugging API calls in Postman gets old fast. I switched to automating all my Notion workflows instead of manual testing.

Set up your Notion connection once in an automation platform and never worry about tokens, endpoints, or formatting again. Plus you can build actual workflows instead of just testing calls.

I handle all my Notion integrations this way now. Way more reliable than manual API calls and you can connect it to other tools too.

Check out Latenode for this - handles all the API complexity and lets you focus on what you actually want to do with your data: https://latenode.com

5

same thing happened to me last week. re-add the integration id to your database permissions even if it looks connected - notion glitches sometimes and the connection breaks without showing it. also double-check you’re in the right workspace. i had mine in the wrong workspace and kept getting 404s.

6

Manual debugging works, but you’re making this way harder than it needs to be with Postman.

Notion’s API is a pain - headers, versions, permissions, formatting. Even when you get it working, it’ll break next week when they update something.

I fought this for months before realizing I was doing it wrong. Ditch the manual API calls and automate everything instead.

Connect Notion once through an integration platform and forget Postman exists. No more 404s, no more header checks, no more copying database IDs.

The platform handles the API mess automatically. You can build actual workflows instead of testing random calls.

I do all my Notion integrations this way now. Connect once, use forever. Way less frustrating.

Latenode makes this easy and handles all the Notion API quirks: https://latenode.com

7

It’s vital to check your Notion-Version header in Postman; it should be set to a date like “2022-06-28” to avoid the object_not_found errors. Often, users overlook this aspect even when everything else appears correct. Additionally, ensure that you are accurately copying the database ID from the URL—look for the 32-character string in the browser; it’s a common error to miss part of it. Lastly, remember to use POST for basic database queries instead of GET, as this misconception can lead to frustrating issues too. If you’re still facing challenges, consider testing a simple page retrieval with a page ID to pinpoint whether the problem lies with authentication or database access.

8

This sounds like a database ID format issue. When you copy the ID from your browser URL, it has dashes, but the API wants the clean 32-character version without any formatting. I ran into this exact same thing switching between Notion endpoints. Strip out all the dashes from your database ID in the request. Also double-check that your integration actually has access to that specific database - I’ve seen cases where it looks connected but the permissions haven’t synced up yet. Wait a few minutes after reconnecting before you test again. That timing thing tripped me up when I first started using their API.