---
title: "Rate Limits"
description: "Understand the rate limits for the Cloud API"
url: https://developer.disguise.one/cloud/rate-limits/
---

# Rate Limits

Disguise Cloud API enforces rate limits to ensure fair usage and to protect the system from abuse. Rate limits are applied per API token.

## Rate Limit Policy

The rate limits for the Cloud API are as follows:

-   **Management API:** 1000 requests per hour
-   **Spaces API:** 1000 requests per hour

**Please Note:** If you exceed the rate limit, you will receive a `429 Too Many Requests` response. You will need to wait until the rate limit resets before making additional requests. It is possible to be rate limited from one API instance and not the other, so you may still be able to make requests to the other API instance.

## Rate Limit Headers

To manage your rate limits effectively, you can use the following headers provided in the API response:

| Header | Description | Values |
| --- | --- | --- |
| **X-RateLimit-Ring3-Status** | Check this header to monitor the current status of your rate limit. | **OK**: You are within the rate limit.<br>**LIMITED**: You have exceeded the rate limit. |
| **X-RateLimit-Ring3-Reset** | Check this header to get the reset time. | If the status is **LIMITED**, this will be a datetime string of when your rate limit resets, otherwise this will be empty |

By using these headers, you can determine when you can make additional requests to the API.

## Handling Rate Limit Exceeded Errors

If you receive a `429 Too Many Requests` response, you should:

1.  Reduce the frequency of your requests.
2.  Implement exponential backoff in your code to retry requests after a delay.
3.  Contact [support](mailto:support@disguise.one) if you believe you need a higher rate limit for your use case.

By adhering to these guidelines, you can ensure that your applications interact smoothly with the Disguise Cloud API without interruption.