Athena
Function_name

RPC compatibility (GET, query-string args)

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.

GET
/rpc/{function_name}

Path Parameters

function_name*string

Header Parameters

X-Athena-Client*string
apikey?string
x-api-key?string

Response Body

application/json

curl -X GET "https://athena-cluster.com/rpc/string" \  -H "X-Athena-Client: string"
{
  "data": [
    {}
  ],
  "count": 0
}
Empty
Empty
Empty

Fetch or update data using a SQLx client (same payload as /gateway/fetch) 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.

RPC compatibility (POST JSON body) POST

Body is either a plain JSON object of named arguments for `function_name`, or a full `GatewayRpcRequest`-shaped wrapper (`function`, `schema`, `args`, `filters`, etc.).