Metadata and SQL endpoints
View as MarkdownIdentity
Section titled “Identity”Framework routes registered under /api/meta and /api/sql when enabled.
Contract
Section titled “Contract”- Metadata routes expose project and registered table schema needed by generated clients.
- Every serialized table column has a semantic
kind. Select options come from the column’s Drizzle enum declaration, andapiWritableis included when the table definition declares an API write restriction. - Browser table code parses the metadata response with the shared
TableSchemaZod contract before using it for display, filter, form-draft, or grid-patch behavior. - SQL query routes return rows; SQL execute routes perform privileged changes.
- SQL bypasses table helpers, trusted-value preparation, reference checks, and ordinary row visibility.
- Registration, authorization, limits, parameters, and dry-run behavior are visible in the running OpenAPI document.