Contracts and schema downloads
These downloads are copied byte-for-byte from the repository's contract owners when the handbook is built. Use the matching source revision and current definition when implementing an integration. A downloaded schema describes shape; it does not provide authorization or prove an operation can execute. See versioning and hard cutovers.
HTTP and reactive descriptions
| Description | Download | Usage |
|---|---|---|
| Application Serving OpenAPI | serving.openapi.json | Serving HTTP |
| Board OpenAPI | board.openapi.json | Board API |
| Reactive AsyncAPI | reactive.asyncapi.json | Reactive channels |
The reference pages render operations, messages and field tables from these same sources. They do not collect credentials or send live requests.
Native messages and configuration
| Description | Download | Exact contract |
|---|---|---|
| Native protocol types | transit-v1.schema.json | Native v1, signed HTTP |
| SQL session routes and messages | sql-session-v1.schema.json | SQL sessions |
| Table mediation messages | table-service-v1.schema.json | Table service |
| Configuration service messages | configuration-v1.schema.json | Configuration |
| Setting keys, defaults and bounds | configuration-settings-v1.json | Configuration reference |
| Structured diagnostics | diagnostic-v1.schema.json | Diagnostics |
| Application installation | application-installation-v1.schema.json | Installation |
These are native schema documents, not OpenAPI routes. Follow each owner's encoding, canonicalization and compatibility rules in addition to validating message structure. Fixed byte arrays, signed values and logical SQL cells must retain their specified representation.
Wire specifications, signing fixtures, SDK ABI declarations, SQL grammars and upstream protocol pins remain in the contract directory. The interface map connects each public surface to its usage reference and internals. Generated files are updated by their owners; the site does not maintain an independent protocol definition.