> 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/developers/management-api/developer-checklist.md).

# Developer checklist

What to confirm before shipping an e6data integration - auth, base paths, polling, pagination, errors, idempotency, propagation, and secrets.

Before you ship an integration against the e6data API, confirm the following.

* **Auth** - choose the right credential (a service token) and send it as `Authorization: Bearer` . A bearer token beats a session cookie. See [Authentication](/query-engine/developers/management-api/authentication.md).
* **Poll, don't assume** - cluster operations and query execution are asynchronous; poll status to a terminal state.
* **Errors** - branch on the error **code**, not just the HTTP status.
* **HTTP/2** - required only for the query path; management REST is plain HTTPS. Don't force curl's `--http2` flag for management calls.
* **Idempotency** - repeating suspend, resume, and scale is safe; **token creation is not** (each call mints a new secret).
* **Propagation** - 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.
* **Secrets** - store tokens in a secret manager, one per consumer, rotate on expiry, and never log or commit them.

## See also

* [Automate clusters, catalogs, schedules, and policies](/query-engine/developers/management-api/automate-clusters-catalogs-schedules-policies.md) - the endpoints and recipes.
* [Connecting to the engine](/query-engine/developers/connecting-to-the-engine.md) - the query path details (HTTP/2, chunks, sessions).


---

# 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/developers/management-api/developer-checklist.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.