> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/account/fetch-rate-limit-status-v1.md).

# GET /api/v1/account/rate-limit

Get rate limit status

Get rate limit status.

`operationId`: `fetchRateLimitStatusV1`

> **Declared server:** `https://api.testnet.nexus.xyz`. Examples follow the OpenAPI operation, path-item, then document server precedence and append the full operation path. A declared URL is not proof of live routing; verify the target deployment before use. See [Networks](/api-reference/guides/networks.md).

> **Not reachable through CCXT.** Rate-limit introspection. CCXT models rate limits client-side from `describe()`, not by asking the venue.

**Authentication:** `hmacAuth`.

Returns the authenticated caller's rate limit tier and, per budget, the ceiling, tokens remaining and reset timestamp — the same data surface as the X-RateLimit-\* response headers, exposed as a queryable resource. This endpoint does not consume a rate limit token, so it can be polled freely to self-manage pacing without depleting the caller's budget. The top-level `limit`, `remaining` and `reset_at_ms` report the **request** class, which for an HMAC key is the binding minimum of the key and owner buckets; for unlimited-tier callers (gateway keys) they are null. `buckets` additionally reports each budget on its own — including `order` and `cancel`, the pools order writes and cancellations are actually charged to — keyed by the same labels a `429` uses, so a client can read its order-placement headroom rather than inferring it from the read budget. WebSocket ceilings are not reported here. See “Rate limits” in the API description.

## Responses

| Status | Body                                                                  | Meaning                                   |
| ------ | --------------------------------------------------------------------- | ----------------------------------------- |
| `200`  | [`RateLimitStatus`](/api-reference/guides/schemas.md#ratelimitstatus) | Current rate-limit status for the caller. |
| `401`  | — *(no schema declared)*                                              | —                                         |

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X GET 'https://api.testnet.nexus.xyz/api/v1/account/rate-limit' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'
```

{% endtab %}

{% tab title="Python" %}

```python
import requests

headers = {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
}

response = requests.get("https://api.testnet.nexus.xyz/api/v1/account/rate-limit", headers=headers)
response.raise_for_status()
print(response.json())
```

{% endtab %}

{% tab title="TypeScript" %}

```typescript
const response = await fetch("https://api.testnet.nexus.xyz/api/v1/account/rate-limit", {
  method: "GET",
  headers: {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
  },
});
if (!response.ok) throw new Error(`${response.status} ${await response.text()}`);
console.log(await response.json());
```

{% endtab %}
{% endtabs %}

`X-Signature` is a placeholder: it is derived from this specific request. See [Authentication](/api-reference/guides/authentication.md) for the canonical string and the HMAC rule.

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.70`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# 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://docs.nexus.xyz/api-reference/account/fetch-rate-limit-status-v1.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.