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
Connect a specific BI tool (Tableau, DBeaver, Superset, Metabase, notebooks)	BI tool recipes
Run existing PySpark workloads against e6data	PySpark compatibility
Manage clusters, catalogs, schedules, and policies from code	Management API

Connecting to the engine

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

Protocol	Use case
JDBC	Java applications, BI tools, drivers that prefer gRPC
PostgreSQL protocol	BI tools that speak Postgres natively
REST API for SQL queries	Any HTTP client, integrations, lightweight scripts
Python connector	Python apps, notebooks, ETL scripts

Authenticating

All programmatic access uses personal access tokens (for individuals) or service account keys (for automation). No long-lived passwords. See Access tokens.

See also

• Connecting to the engine - protocols and connection strings.
• Management API - automate clusters, catalogs, and policies.
• Access tokens - credentials for programmatic access.