OpenAPI Reference

The sanitized OpenAPI publication is temporarily paused while the application release catches up with this documentation release.

Do not generate a client from a previously cached Leenops OpenAPI file. During today's tests, use the four dedicated endpoint guides and Public API Status, or use live MCP tool discovery for broader coverage.

The next published OpenAPI document is constrained to the supported public REST contract: 7 paths and 17 HTTP operations for contacts, deals, projects, and issues/tasks. Routes that are not listed in Public API Status are not a supported public REST contract.

Publication requirements

Area	Coverage
Supported paths and methods	Complete
Authentication	Bearer API key
Path and discovered query parameters	Included
Request fields	Generated from runtime validation where possible
Common success and error envelopes	Included
Response entity fields	Generic for some operations
Support contact	`support@leenops.com`

Publication is gated until the generated file excludes private route inventory, source-file locations, validator identifiers, database names, and other implementation metadata. Those details are not required to integrate and are not part of the public contract.

Use it safely

Wait for this page to expose an official download link before generating a client.
Generate a client only for operations present in that file.
Read the linked endpoint guide before sending a mutation.
Treat runtime 400 or 422 validation as authoritative if a generated schema is more permissive.
Send API keys only to https://workspace.leenops.com.
Regenerate the client when the OpenAPI info.version changes.

Do not infer undocumented fields, internal routes, or database structure from response data. For a missing operation, retrieve the live MCP catalog or email support@leenops.com.