API changelog
See what the API, the webhooks and the MCP server offer today and when each part arrived.
Updated 23 September 2026
- Why
- An integration you build today should keep working, and you should know what is new.
- What
- The API's own history: every change so far has been an addition, and nothing shipped has been renamed or removed.
- How
- Read the entries since you last built against the API; the paths stay under
/api/v1.
Where it stands
The REST API is v1 and its OpenAPI document is version 1.0.0: 23 operations and 14 scopes, with 22 webhook events and 8 inbound actions. Scope, event and action names only ever grow.
History
| Date | What arrived |
|---|---|
| 2026-06-10 | API keys with scopes. POST /api/v1/products/bulk and GET /api/v1/products. Signed outbound webhooks for quotes, orders and service items. |
| 2026-06-12 | Quotes, orders, customers and requests on v1, with their scopes and the OpenAPI document. Inbound endpoints: create request, upsert customers and upsert products. The MCP server at /api/mcp. The Slack and Teams body formats. |
| 2026-06-13 | The quote.declined and order.updated events. |
| 2026-06-23 | The ERP order status inbound action. |
| 2026-08-27 | The design.saved, design.exported, quote.superseded, quote.expired, quote.viewed and order.invoiceable events. The order invoice inbound action. |
| 2026-09-20 | Stock: stock:read, stock:write, the stock lines, locations and movements routes and two MCP tools. Source: suppliers:read, purchase_orders:read, their routes, the two purchase_order events and two inbound actions. Route: deliveries:read, the deliveries routes, five delivery events, the delivery status action and list_deliveries. Monitoring: monitor.fired. |
Each date is the day the change reached the codebase, from its history.
Related
- The REST APICall every v1 resource with the right scope, page through lists and handle every error it returns.
- WebhooksReceive signed events at your own URL and prove each one came from Kabaido.
- The MCP serverConnect Claude or any MCP client to your workspace, with the scopes you choose.
- Inbound endpointsGive any system a URL it can post JSON to, and choose what each post does.