> 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/readme-2.md).

# Overview

Connect to e6data programmatically or query it - JDBC, REST API, PostgreSQL protocol, Python, PySpark - and automate it with the Management API.

This section covers connecting to e6data from code and external tools, and automating e6data resources.

## Query vs. automate

| You want to…                                                                 | Go to                                                                            |
| ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Run SQL from an app, BI tool, or notebook                                    | [Connecting to the engine](/query-engine/developers/connecting-to-the-engine.md) |
| Connect a specific BI tool (Tableau, DBeaver, Superset, Metabase, notebooks) | [BI tool recipes](/query-engine/developers/bi-tool-recipes/tableau.md)           |
| Run existing PySpark workloads against e6data                                | [PySpark compatibility](/query-engine/developers/pyspark-compatibility.md)       |
| Manage clusters, catalogs, schedules, and policies from code                 | [Management API](/query-engine/developers/management-api.md)                     |

## Connecting to the engine

One endpoint speaks three protocols - pick whichever is easiest for your client:

| Protocol                                                                                          | Use case                                              |
| ------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| [JDBC](/query-engine/developers/connecting-to-the-engine/jdbc.md)                                 | Java applications, BI tools, drivers that prefer gRPC |
| [PostgreSQL protocol](/query-engine/developers/connecting-to-the-engine/postgresql-protocol.md)   | BI tools that speak Postgres natively                 |
| [REST API for SQL queries](/query-engine/developers/connecting-to-the-engine/rest-api-for-sql.md) | Any HTTP client, integrations, lightweight scripts    |
| [Python connector](/query-engine/developers/connecting-to-the-engine/python-connector.md)         | Python apps, notebooks, ETL scripts                   |

## Authenticating

All programmatic access uses [personal access tokens](/query-engine/guides/security/access-tokens/pat-and-service-account-keys.md) (for individuals) or [service account keys](/query-engine/guides/security/access-tokens/pat-and-service-account-keys.md) (for automation). No long-lived passwords. See [Access tokens](/query-engine/guides/security/access-tokens.md).

## See also

* [Connecting to the engine](/query-engine/developers/connecting-to-the-engine.md) - protocols and connection strings.
* [Management API](/query-engine/developers/management-api.md) - automate clusters, catalogs, and policies.
* [Access tokens](/query-engine/guides/security/access-tokens.md) - credentials for programmatic access.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.e6data.com/query-engine/developers/readme-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.