Skip to main content
The OpenAPI 3.1 document describes the HAIP 2 draft HTTP API and its JSON schemas. Its revision is 2.0.0-draft.3. It is a draft contract and does not establish a production deployment. Use the documented credential scope for each operation. Producer and publisher bearer credentials cannot call human confirmation endpoints. Human mutations require the authenticated browser session, CSRF token and exact trusted Origin. The @haip/protocol draft package also exports @haip/protocol/schema.json and @haip/protocol/openapi.json. The source contracts live under protocol/draft-2.0.0-3 in the repository. Generated TypeScript declarations are derived from that schema rather than defining a separate wire format. Start with the review lifecycle and HTTP transport before implementing the API. HAIP 1’s archived OpenAPI document describes a different, unsupported protocol.