Provision a database with the Athena schema
Runs the bundled provisioning SQL against either a direct `uri` or a registered `client_name`. When `register` is true and `uri` is provided, the client is added to the runtime catalog after provisioning.
Header Parameters
The static admin key configured as ATHENA_KEY_12. Authorization headers (Bearer <key>), X-API-Key, X-Athena-Key, or ?api_key= are also accepted.
Request Body
application/json
Direct Postgres URI to provision (mutually exclusive with client_name).
uriRegistered client whose URI will be used (mutually exclusive with uri).
When true and uri is provided, register the client in the runtime catalog.
falseOptional client name when registering (defaults to "provisioned").
Response Body
application/json
curl -X POST "https://athena-cluster.com/admin/provision" \ -H "apikey: string" \ -H "Content-Type: application/json" \ -d '{}'{
"statements_executed": 0,
"client": "string",
"registered": "string",
"tables": [
"string"
]
}List runtime Postgres connection pool statistics and health GET
Returns per-client pool runtime snapshots (init time, usage) plus sqlx pool metrics (size, idle, active, max) when available. Admin-only.
List or create durable Postgres clone jobs GET
Returns redacted control-plane state for Athena-managed Postgres clone jobs.