> For the complete documentation index, see [llms.txt](https://doc1.antgst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc1.antgst.com/readme/rate-limits.md).

# Rate Limits

A rate limit is the number of API calls that can be made within a given time window. Actions such as rapidly updating configuration settings, aggressive polling, or making highly concurrent API calls may result in your account being rate limited.

All API requests are subject to rate limits. Real-time rate limit usage statistics are described in headers that are included with most API responses. When requests get blocked, responses with HTTP status `-32`(Too Many Requests) are returned.

Each API endpoint, or each group of API endpoints has a rate limit policy.

## Messaging API Rate Limits

|                   Endpoint                  |   Rate Limit Policy  |
| :-----------------------------------------: | :------------------: |
|   POST <https://api.antgst.com/sms/txt/2/>  | 200 rps, per account |
|    POST <https://api.antgst.com/sms/hlr/>   |  60 rps, per account |
|      POST <https://api.antgst.com/call>     | 200 rps, per account |
|   POST <https://api.antgst.com/sms/txt/3/>  |  60 rps, per account |
| POST <https://api.antgst.com/user/account/> | 200 rps, per account |

\
Most endpoints are rate limited to 200 rps (requests per second) per account.

OTP messaging API endpoints' usage statistics are measured separately, but you should not use both of them at a high rate at the same time. The /sms/txt/3/send/json​ endpoint can accept requests at a rapid rate of 200 rps, while ANT submits these messages to the channel API at a lower rate of 60 rps.


---

# 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://doc1.antgst.com/readme/rate-limits.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.