> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/api-reference/api-reference/openapi-spec.md).

# OpenAPI Specification

Download the published Nullify API specification:

{% file src="/files/1NgvLK12PRq7RFdn97yd" %}

## What the download covers

The bundle combines the committed public specifications selected by the production service-version manifest. Operations tagged `Private`, every operation under `/internal` or `/cli`, and schemas left unreferenced after that filtering are excluded. Internal service-to-service routes and the routes the `nullify` CLI uses are not part of the public contract and can change without notice. A service with no committed public specification contributes no operations.

This is the published integration contract, not an inventory of every internal route or every feature in development. A route in the bundle can still require a particular tenant entitlement, connector, role, or enabled feature. Your deployment may be on a different version.

Shared schema names are reconciled during bundling; conflicting definitions can be resolved to one selected definition. If an example or generated client disagrees with your tenant's response, retain the response and request details (without credentials) and contact Nullify before relying on an ambiguous field.

The reference pages explain customer workflows and link to the bundle for parameters, request bodies, and response types. Do not infer an undocumented endpoint by copying a path pattern from another service.