> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/limits-and-quotas/api-limits.md).

# API limits

Behaviors that shape API usage in e6data - pagination, result chunking, async polling, idempotency, and eventual consistency.

The e6data API doesn't publish fixed request-rate quotas, but several behaviors shape how you build against it. See [Management API](/query-engine/developers/management-api.md) and the [developer checklist](/query-engine/developers/management-api/developer-checklist.md).

## Pagination and results

| Aspect              | Behavior                                                                                                                                                            |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| List endpoints      | Return `{ items, total }` - page through with the provided paging                                                                                                   |
| Large query results | Arrive as numbered chunks (`…/result/chunks/{n}`) on the query path                                                                                                 |
| Editor display      | The SQL Editor shows the first 10,000 rows; use a connector or `COPY INTO` for more - see [Query limits](/query-engine/reference/limits-and-quotas/query-limits.md) |

## Asynchronous operations

* **Poll, don't assume.** Cluster operations and query execution are asynchronous - poll status to a terminal state rather than treating the first response as final.
* **Idempotency.** Repeating suspend/resume/scale is safe; **token creation is not** (each call mints a new secret).

## Consistency and transport

* **Eventual consistency.** Token revocations and permission changes are cache-backed and can take a short time to take effect - design retries and rotations around eventual, not instant, consistency.
* **HTTP/2** is required on the query and gRPC paths; management REST is plain HTTPS.

## See also

* [Management API](/query-engine/developers/management-api.md)
* [Developer checklist](/query-engine/developers/management-api/developer-checklist.md)
* [Query limits](/query-engine/reference/limits-and-quotas/query-limits.md)


---

# 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.e6data.com/query-engine/reference/limits-and-quotas/api-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.