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 and the developer checklist.

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

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
• Developer checklist
• Query limits