API reference

The HTTP API behind Tearleads clients. Document and key material is end-to-end encrypted, so request bodies carry ciphertext, signed manifests, and key envelopes that only the client SDK can produce or open.

This document is generated from the Zod operation registry in @tearleads/validators, which remains the runtime authority. Rules that JSON Schema cannot express are listed per operation under x-tearleads-runtime-refinements. See the protocol specification for message semantics, proofs, and failure handling.

Because documents and keys are end-to-end encrypted, the client SDK is the only practical client: this reference is for reviewing what the server accepts, returns, and enforces, not for writing a client.

These pages are rendered from that OpenAPI document, which is generated from the Zod operation registry; the Zod schemas stay the runtime authority. Message semantics and proofs are in the protocol specification, and protocol terms link to the glossary.