Confluence currently does not publish rate limits despite the API returning rate limit responses at times. The current rate limiting guidance explains that rate limits are not published because rate limiting is implemented by concurrency and resource limits. However, there are use cases, such as migrations, where apps need to know the rate of API calls that can be safely made before rate limiting may be applied.

Note: There is an equivalent request for Jira: https://ecosystem.atlassian.net/browse/ACJIRA-2255

Additional reference:

• Atlassian Rate Limiting Overview: Rate limiting policy, including how rate limits are calculated and managed.
• Rate Limit Related Headers: Description of the headers related to rate limiting, such as Retry-After, X-RateLimit-Reset, and X-RateLimit-NearLimit.
• Request Backoff: Guidance on how to handle rate-limited responses, including best practices for retrying requests.