Execute SQL via driver (gateway alias)
Same request body and behavior as `POST /query/sql`. Provided for SDKs that target a `/gateway/*` prefix. PostgreSQL driver behavior: - `X-Athena-Client` or direct PostgreSQL URI headers (`x-pg-uri` preferred; `x-athena-jdbc-url` / `x-jdbc-url` compatibility). - Direct URI auth bypass requires URI username + password credentials. - Non-PostgreSQL drivers keep standard auth requirements. - Optional `schema_name` is supported only for the PostgreSQL driver and configures execution search_path as `schema_name, public`.
Header Parameters
Registered Athena client name for client-routed execution.
Preferred direct PostgreSQL URI (postgres://... or jdbc:postgresql://...) for driver=postgresql.
Compatibility direct PostgreSQL URI header.
Compatibility direct PostgreSQL URI header.
Required for non-PostgreSQL drivers and for PostgreSQL requests without credentialed direct URI bypass.
Request Body
application/json
"athena" | "postgresql" | "supabase"Optional schema override; supported only when driver is postgresql.
Response Body
application/json
curl -X POST "https://athena-cluster.com/gateway/sql" \ -H "Content-Type: application/json" \ -d '{ "query": "string", "driver": "athena", "db_name": "string" }'{}Execute a Postgres function as an RPC call POST
Invokes `schema.function(arg => ...)` on the pool selected by `X-Athena-Client`. Requires API key with right `gateway.rpc.execute`. Success responses return **`{"data": [...], "count": ...}`** (not the usual `status`/`message` envelope). Rows are JSON objects keyed by selected columns.
Update data POST
Applies updates to rows matching supplied conditions. Payload shape mirrors fetch-style condition blocks so callers can reuse filtering logic between read and write flows. Supports optional post-processing fields for response shaping where applicable. Supports `X-Athena-Client` or direct PostgreSQL URI headers (`x-pg-uri` preferred); direct URI requests execute inline.