> ## Documentation Index
> Fetch the complete documentation index at: https://hc.saas-manager.biz.nuro.jp/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> The API implements rate limiting to ensure fair usage and system stability. Guidelines vary by endpoint, but please follow the guidelines below:

## Rate Limiting Overview

* For polling operations (checking request status), leave at least 1 second between requests
* When a rate limit response occurs, implement exponential backoff
* Check response headers to monitor rate limit information

## Rate Limit Headers

The API returns the following headers to provide information about rate limits:

| Header                  | Description                                              |
| ----------------------- | -------------------------------------------------------- |
| `X-RateLimit-Limit`     | Maximum number of requests in a given period             |
| `X-RateLimit-Remaining` | Number of requests remaining in the current period       |
| `X-RateLimit-Reset`     | Unix timestamp when the current rate limit window resets |

## Response When Rate Limit is Exceeded

When the rate limit is exceeded, an HTTP 429 Too Many Requests response is returned:

```json theme={null}
{
  "statusCode": 429,
  "errorId": "rate_limit_exceeded",
  "message": "Too Many Requests"
}
```

## How to Handle Rate Limit Exceedance

1. Use the `Retry-After` value in the response header to determine retry time
2. Implement an exponential backoff algorithm to gradually increase retry intervals
3. If necessary, review how you use the API

## Best Practices

* Implement rate limit handling in API clients
* Adjust request frequency when approaching rate limits
* Implement retry logic considering rate limits for important operations