Clarification Required on Confluence REST API Rate Limiting and Migration Header Requirements

I am currently evaluating the Confluence REST API limits and behaviour for integration with our systems. I would appreciate your assistance clarifying a few key points related to rate limiting and migration headers. Specifically, I would like to confirm the following:

  1. API Rate Limit Per Plan Tier
    The documentation mentions a rate limit of 6,000 requests per minute.
    • Could you please clarify if this limit applies uniformly across all Confluence plan tiers (Free, Standard, Premium, Enterprise)?
    • Additionally, is this limit calculated per tenant (i.e., per Confluence site), per user, or globally across all users in a tenant?
  2. Direction of Rate Limiting
    • Is this rate limiting applicable only to requests made from client applications to the Confluence REST API?
    • Or does it also apply to outbound calls initiated from Confluence (e.g., webhook requests or app requests to our external servers)?
  3. Use of Migration Header (Migration-App: true)
    • Is the use of the Migration-App: true header mandatory for all API calls, or is it only required for specific use cases (e.g., bulk data migration or app provisioning)?
    • What are the implications if this header is omitted in scenarios that involve high-volume or admin-level operations?

These clarifications will help us better plan our integration and ensure compliance with Atlassian’s rate limiting and security policies.