Athena
V1Table

Insert or upsert rows via the REST gateway

Accepts a single object or array payload. Set `Prefer: return=minimal` for HTTP 204 responses and `Prefer: resolution=merge-duplicates` for upserts.

POST
/rest/v1/{table}

Path Parameters

table*string

Header Parameters

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

Use return=minimal for 204 or resolution=merge-duplicates for UPSERT.

Request Body

application/json

Response Body

application/json

curl -X POST "https://athena-cluster.com/rest/v1/string" \  -H "X-Athena-Client: string" \  -H "apikey: string" \  -H "Content-Type: application/json" \  -d '{}'
{
  "data": [
    {}
  ]
}
Empty
Empty
Empty

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.

Run a config-driven pipeline (source → transform → sink) POST

Executes a pipeline with optional prebuilt reference and overrides. `source.client` and `sink.client` override the Postgres/Supabase pool per step; when omitted, `X-Athena-Client` is used. Optional column aliasing and `dry_run` are supported. When gateway API keys are enforced, the key is validated against `X-Athena-Client`; step client overrides still route fetch/insert to other registered clients if specified. Successful runs emit three rows to `pipeline_step_log` on the configured logging database (`gateway.logging_client`), correlatable via `pipeline_run_id` in the response.