> For the complete documentation index, see [llms.txt](https://sway-technologies.gitbook.io/sway-charts-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sway-technologies.gitbook.io/sway-charts-api-documentation/rest-api-specification/getting-started/rate-limits-and-throttling.md).

# Rate Limits & Throttling

The Sway Charts REST API supports per-client configurable maximum API access rate. This rate limits how frequently the API can be accessed. There are three types of rate limits:

* For login requests based on IP of the request. Default value 1 per second
* For 'get data' requests based on client session, default value 2 per second.
* For trading requests(placing / modifying / canceling orders) based on client session, default value 1 per second. Default value permits accessing each resource available to client no faster than once a second.

If access rate is exceeded, the server responds with the `429 Too Many Requests`.


---

# 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://sway-technologies.gitbook.io/sway-charts-api-documentation/rest-api-specification/getting-started/rate-limits-and-throttling.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.