Routing Model
How Athena resolves clients and routes requests.
Primary Routing Header
Athena resolves target clients using:
X-Athena-Client(logical client name)
This selects the configured backend connection for gateway, query, and many admin operations.
Optional Direct Routing Inputs
X-JDBC-URL/x-athena-jdbc-url: direct PostgreSQL routingx-supabase-url+x-supabase-key: custom Supabase request routing
Wildcard Host Routing
With wildcard routing enabled, Athena can infer client context from request hostnames.
Example pattern:
*.v3.athena-db.comWhen active, route metadata maps host labels to internal client names.
Public Route Dispatch
Athena also supports curated public operations:
POST /public/{route_key}/{op}
Route keys map to controlled backend operations for external consumers.