Last updatedMay 17, 2021

Rate this page:

Rate limiting

This page provides details about rate limiting in Confluence for app migration, and can help you understand how to anticipate rate limiting and manage how your app responds.

There are currently no rate limits specific to app migration in Jira.

Required app migration header

In order to ensure your app migration code does not impact any other Confluence customer on the same shard, you must provide each request to any Confluence REST API with the HTTP header Migration-App. You can use any value with this header.

See an example

1
Migration-App: true

Warning

Use this header to ensure that your migration path does not impact customers, and avoids the possibility that your app key can be banned from app migration.

Current rate limits

The table below details the current rate limits in Confluence.

LimitFrequencyTime
6000 requestsper app per tenantone minute
12000 requestsper tenantone minute

Managing requests

As with all web requests, you may receive HTTP 429 Too Many Requests responses.

We do not expect more than two concurrent Confluence apps to make calls to our APIs during a migration. However, in order to prepare for the possibility that this may happen, all apps need to implement the retry policy of rate limiting responses.

Rate this page: