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
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
Last modified on September 29, 2026
