Rate limit waits in the response body
By Steven Van ·
Notion API rate-limit errors now include the retry wait in the response body for clients that can't read headers.
The 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.