Can you explain how the notion api rate limits are calculated per integration token versus per workspace so I can design my sync script efficiently?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Can you explain how the notion api rate limits are calculated per integration token versus per workspace so I can design my sync script efficiently?
1 real search · 1 real-search pass
Notion API rate limits per integration token versus workspace shared limit official documentationGoogle ↗
OBSERVEDComparison
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model).
Searches and sources
ChatGPT1 real searches · gpt-6
Notion API rate limits per integration token versus workspace shared limit official documentation Google ↗
- Faster retries and plan-based rate limits · creatorstoolbox.com
- New Notion API Changelog Entry: September 9, 2026 · Issue #395 · ramnes/notion-sdk-py · github.com
- Notion Rate Limits: 180 per minute per connection · jitterflow.io
- Notion API for AI Agents: Endpoints, Permissions & Safe Access · bollardai.com
- No more tool-specific Notion MCP rate limits · creatorstoolbox.com
- Notion API – Request limits · developers.notion.com
- Notion API – Database queries · developers.notion.com