One specification, four ways in
cashwerk has no separate integration products with their own behaviour. There is one REST API, and everything else is derived from it.
The OpenAPI specification is the contract. Every public endpoint is in it, with fields, error codes and scopes. When an endpoint changes, the specification is re-exported, the MCP server and the n8n node are regenerated from it, and a check in CI blocks any state in which the three drift apart. That is why we do not quote a number of endpoints or tools: on any given day it is whatever the specification says.
For your own integrations you use an API key with scopes or, in the Enterprise plan, an OAuth 2.0 client with a consent flow. Webhooks report events to your system, with retries and a delivery log. If you do not want to code, take the n8n node; if you work with an AI client, connect the MCP server via OAuth. All four paths pass through the same security chain and the same org-scoped commands as the interface.
The embeds belong to the platform as well: the booking widget for your website, public forms and public document links. What is still missing is at the top of the page: a developer portal with guides, test tenants, SDKs, an app marketplace and a versioned API changelog. Until then the reference is the OpenAPI documentation.
