Skip to main content
Use a Flight SQL client SDK to execute SQL and receive Arrow results. Every client sends the same three connection values:
  • The Flight SQL endpoint: sql.parable.work:443 in production or sql.staging.parable.work:443 in staging, with TLS.
  • authorization: Bearer <token>.
  • x-tenant: <workspace-slug>.
A member whose role can query the Provider Pools creates a SQL token in Protection → Access Tokens. Query Provider Pools with SQL walks through the role, the token, and a first query in DBeaver or Python.
The Workspace API SDKs expose resource operations. SQL uses Flight SQL client SDKs because query results stream as Arrow data.

Install a client

There is no published TypeScript Flight SQL client yet.

Query Provider data

Set PARABLE_API_TOKEN and PARABLE_WORKSPACE, then provide the endpoint in the form expected by your client:
  • Rust uses PARABLE_FLIGHT_URL=https://sql.parable.work.
  • Python ADBC uses PARABLE_FLIGHT_URL=grpc+tls://sql.parable.work:443.
  • Go uses PARABLE_FLIGHT_ENDPOINT=sql.parable.work:443.
Replace the table and columns with values from catalog discovery.

Keep queries portable

  • Use fully qualified names such as providers.google.users.
  • Discover schemas instead of assuming that a Provider or stream is enabled.
  • Treat results as Arrow data and preserve its types until the application boundary.
  • Use prepared statements when a value comes from user input.
See SQL behavior for the shared language contract and Flight SQL for protocol operations and client capability negotiation.