Schema and Introspection

Schema Routes

Athena schema endpoints:

• GET /schema/clients
• GET /clients (alias)
• GET /schema/tables
• GET /schema/columns
• GET /schema/constraints
• GET /schema/migrations
• GET /debug/schema

Registry and Router Routes

Operational registry surfaces:

• GET /router/registry
• GET /registry
• GET /registry/{api_registry_id}

Auth requirements

Schema, client list, registry, router registry, and bundled OpenAPI YAML routes require admin or gateway authentication (require_admin_or_gateway): either ATHENA_KEY_12 via X-Athena-Key / X-Athena-Admin-Key, or a valid ath_* key with read-appropriate gateway rights (same pattern as other protected metadata).

You still send X-Athena-Client where the handler needs a logical client for Postgres-backed introspection.

GET /debug/schema uses the configured gateway.logging_client from server config and reports:

• Observed tables/columns from the live logging catalog.
• Runtime-expected logging tables/columns.
• Missing required/optional items and relation-type mismatches.
• Overall health (healthy, warning, degraded, unhealthy).

Details: Security, auth ordering, and rate limits.

Use Cases

• Build dynamic table browsers in internal tools.
• Drive migration dashboards from /schema/migrations.
• Resolve available logical routes and route metadata from registry endpoints.

Reference

Use Reference -> Athena API Reference -> schema, registry, router, and clients sections.

Operation Links

• GET /schema/clients
• GET /clients
• GET /schema/tables
• GET /schema/columns
• GET /schema/constraints
• GET /schema/migrations
• GET /debug/schema
• GET /router/registry
• GET /registry
• GET /registry/:api_registry_id