# Rate limit waits in the response body

By Steven Van · 2026-09-24

Notion API rate-limit errors now include the retry wait in the response body for clients that can't read headers.

The [Notion](<https://creatorstoolbox.com/tools/notion>) API now repeats rate-limit wait times in the response body. Any 429 or 529 response that includes a Retry-After header now also puts that wait in **additional\_data.retry\_after** as a string of whole seconds, so clients that can't read response headers, such as MCP clients, can still see how long to wait.

Two new rate\_limit\_reason values are also available: **public\_api\_endpoint\_rate\_limit** for an endpoint's own limit, and **public\_api\_request\_blocked** for a connection whose API access has been restricted, where retrying won't help. A workspace-limit 429 now states that the limit is shared by all of the workspace's connections. See the [request limits documentation](<https://developers.notion.com/reference/request-limits#rate-limit-responses>).

![Notion](<https://www.google.com/s2/favicons?domain=notion.so&sz=128>)

Notion

All-in-one workspace for notes, docs, projects, and wikis — with AI built in for writing, summarizing, and organizing.

[View Notion →](<https://creatorstoolbox.com/tools/notion>)

[Read the original announcement →](<https://developers.notion.com/reference/request-limits#rate-limit-responses>)

[Read Rate limit waits in the response body on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-rate-limit-waits-in-the-response-body>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-rate-limit-waits-in-the-response-body