Update data
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.
Header Parameters
Registered Athena client name. Optional when direct PostgreSQL URI headers are provided.
Preferred direct PostgreSQL URI (postgres://... or jdbc:postgresql://...).
Compatibility direct PostgreSQL URI header.
Compatibility direct PostgreSQL URI header.
optional API key mirror of the apikey header
Required when X-Athena-Client is custom_supabase
uriRequired when X-Athena-Client is custom_supabase
Request Body
application/json
Column name to group results by
Time granularity for grouping timestamp data
"day" | "hour" | "minute"Column to aggregate (required when using aggregation_strategy)
Aggregation strategy to apply (requires aggregation_column)
"cumulative_sum"Whether to deduplicate during aggregation
Response Body
application/json
curl -X POST "https://athena-cluster.com/gateway/update" \ -H "Content-Type: application/json" \ -d '{ "table_name": "app_events", "conditions": [ { "eq_column": "id", "eq_value": "5d845b27-8d06-40a0-9e76-08de9d9f3c1f" } ], "update_body": { "source": "api" } }'{
"status": "success",
"message": "Rows updated",
"data": {
"affected_rows": 1
}
}Execute SQL via driver (gateway alias) POST
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`.
Compatibility RPC endpoint for Postgres functions GET
Same execution as `POST /gateway/rpc` with `function` taken from the path. Query keys: `schema`, `select`, `count`, `limit`, `offset`, `order` (`column` or `column.desc`). Other keys are either RPC arguments or filters written as `column=op.value` (e.g. `status=eq.active`). Arrays use `{a,b}` in the value portion.