Skip to main content
ExplanationApplies to: Unified engine deployments
Use HTTP to query data, save workloads, run notebooks, refresh dashboards, manage catalogs, and inspect execution. The same engine services handle requests from the console and from your own clients.

​
Start here

  1. Make your first request to discover this instance.
  2. Query inline orders to open a session, submit SQL, and read real results.
  3. Create and run a workload to save a task graph and follow a run.
  4. Browse the complete API reference for every public operation.
Read the endpoint description and parameters beside its request and response examples. Copy request examples into your own client.

​
Choose an API area

Secrets, credentials, native streaming pipelines, and SQL table maintenance use SQL through session operations. See SQL-managed features for complete request flows.

​
Read and run examples

Complete examples show requests in order. Copy requests into your own client and replace the placeholders with your deployment values. Keep returned IDs for later steps. Repeat status reads until execution reaches a final state. Decode Arrow results with a compatible client. Saved resources and started work remain in the engine after you leave the documentation.

​
Download the contract

Download the OpenAPI contract. The OpenAPI document is generated from the HTTP endpoint inventory, shared input schemas, and Rust response DTOs. Examples are illustrative; inspect your engine’s actual response in your client.
Last modified on November 4, 2026