# API rate limits

#### Jira API rate limits outline the platform’s built-in constraints that can affect how Xopero ONE protects and restores your data.

***

## Overview

Sending a large number of requests in a short period can overload or destabilize the application. To avoid this, **Jira** controls how many requests you can send within a specific time window. If you reach this limit, **Jira** temporarily blocks further requests until the limit resets to ensure stable platform performance and protect the system against accidental, or intentional misuse.

{% hint style="info" %}
For detailed information about current rate limits, see [the official Jira documentation](https://developer.atlassian.com/server/hipchat/hipchat-rest-api-rate-limits).
{% endhint %}

***

## Backup

Organizations using **Jira free** or **standard** plans are subject to a restriction that enforces a minimum backup interval of **6 hours**.

To comply with this limitation, you should schedule backups at intervals of **at least 6 hours and 1 minute**. If you attempt to run backups more frequently, **Jira** will return an error message indicating that the operation cannot be performed.

{% hint style="danger" %}
Scheduling backups at exactly 6 hours may cause problems due to small differences in system time or processing delays. To ensure smoother operations and avoid scheduling conflicts, set the interval **to more than 6 hours**.
{% endhint %}

{% hint style="success" %}
**Jira** premium organizations have no limits.
{% endhint %}

<figure><img src="https://319733277-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0CBTl43C3OO6ySL1DJ6k%2Fuploads%2Fl7w5hhvbEDd4fkKKpXte%2Fimage.png?alt=media&#x26;token=147dec5e-f592-4003-955c-c22d1260982d" alt=""><figcaption></figcaption></figure>

***

## Recovery

A single **Jira** instance supports a maximum of **100 restoration operations**. Any attempt to exceed this limit cannot be processed because of constraints in the **Jira** API.

{% hint style="warning" %}
This restriction is not officially documented by **Atlassian**. It was identified during internal testing and confirmed through operational observations.
{% endhint %}