> For the complete documentation index, see [llms.txt](https://helpcenter.xopero.com/xopero-one-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.xopero.com/xopero-one-en/compliance-and-risk-management/avoiding-api-rate-limits-impact/reducing-bitbucket-api-limits-impact.md).

# Reducing Bitbucket API limits impact

## Adding additional users to Xopero ONE <a href="#additional_users" id="additional_users"></a>

**Xopero ONE** lets you authenticate multiple organization accounts when backing up repositories. By distributing provider-imposed request limits across several accounts, the backup process is accelerated and the risk of throttling—minimized.

For step-by-step instructions on adding additional accounts to a backup, refer to the [**Throttling prevention** section](/xopero-one-en/compliance-and-risk-management/throttling-prevention.md) of the knowledge base.

***

## Limiting the number of simultaneously secured repositories <a href="#limiting_the_number_of_simultaneously_secured_repositories" id="limiting_the_number_of_simultaneously_secured_repositories"></a>

To optimize performance, limit the number of repositories secured simultaneously by creating multiple backup plans for **Bitbucket**. Configure their schedules so that they run at defined intervals rather than all at once.

For example, if your organization contains 900 repositories, you can create four backup plans and assign 225 repositories to each. Depending on your needs, you may schedule these plans to run daily at 6-hour intervals, or configure each plan to run on a different day of the week.

***

## Scheduling copies outside CI/CD task runtime <a href="#scheduling_copies_outside_of_cicd_tasks_runtime" id="scheduling_copies_outside_of_cicd_tasks_runtime"></a>

All CI/CD task activity also consumes query limits, which are shared with the **Xopero ONE** application. To avoid conflicts, it is recommended to schedule backups outside CI/CD operating hours— for example, during the night.

***

## Excluding unnecessary metadata in the plan <a href="#excluding_unnecessary_metadata_in_the_plan" id="excluding_unnecessary_metadata_in_the_plan"></a>

When creating a backup plan, you can select which data should be secured. By default, all data types in the plan are included. However, if you know that certain elements—such as variables or pull requests—will not be needed for future recovery, you can deselect them from the list. Backing up less data reduces the number of sent queries and improves overall efficiency.

<figure><img src="/files/UD3jZGIzwLmxkyAVzTuM" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpcenter.xopero.com/xopero-one-en/compliance-and-risk-management/avoiding-api-rate-limits-impact/reducing-bitbucket-api-limits-impact.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.