Query a table using PostgREST-style filters
Mirrors the Supabase PostgREST query syntax. Supply filter expressions (`column.eq=value`, `column.lt=value`, `or=(cond1,cond2)`, etc.), `select`, `limit`, `offset`, `order`, and the optional `Range` header (`items=0-24`). The handler also honors `Prefer: return=minimal`.
Path Parameters
Target table name (sanitized before execution).
Query Parameters
PostgREST select clause (comma separated columns).
Maximum number of rows to return (default 100).
Row offset (default 0).
Column ordering using .asc/.desc (e.g. id.desc).
PostgREST or expression to build grouped filters ((a.eq.1,b.eq.2)).
Header Parameters
Selects which Postgres pool executes the query.
Gateway API key (can also be passed via Authorization or x-api-key).
Mirror of apikey useful for proxies.
Optional items=start-end range header that overrides offset/limit.
Response Body
application/json
curl -X GET "https://athena-cluster.com/rest/v1/string" \ -H "X-Athena-Client: string" \ -H "apikey: string"{
"data": [
{}
]
}Delete rows using PostgREST-style filters DELETE
Filters are mandatory. Use the same query syntax as GET and include `Prefer: return=minimal` for HTTP 204 responses.
Update rows filtered via PostgREST expressions PATCH
Filters are required (`column.eq=value`, `column.lte=value`, `or=(...)`). The request body must be an object describing the columns to patch. `Prefer: return=minimal` controls whether the response returns data.