Changelog

Dated entries, newest first. Anything that would break an existing integration is called out explicitly.

Additions are not breaking: a new field on a response, a new optional parameter, a new enum member, or a new endpoint. Build clients that ignore fields they do not recognise and tolerate unknown enum values, and these land without your involvement.

2026-09-22 — Reads for tickets, bookings and services

Added

• GET /tickets, /tickets/{id} and /tickets/{id}/history. Filter by status, priority, category and customerId; search matches the subject and description by substring and a reference (T-… or the pipeline card’s TK-…) exactly.
• GET /bookings and /bookings/{id}, with inclusive from/to day bounds.
• GET /services, /services/{id}/resources, and /services/{id}/resources/{resourceId}/availability. Availability accepts at most 31 days per request.
• cursor on the customers, conversations, tickets and bookings lists, so a sync can page without risking skipped rows.
• This documentation site. The reference is generated from the running API, so it cannot describe an endpoint that does not exist or miss one that does.

Notes

• A booking’s date, startTime and endTime are the organization’s local wall clock, not instants. Availability slots are instants.
• A sync reports creations and changes, not removals. See syncing.

2026-09-19 — Reads for customers and conversations

Added

• GET /customers and /customers/{id}.
• GET /conversations, /conversations/{id} and /conversations/{id}/messages, with the AI summary on a resolved conversation once it has been written.
• Organization API keys with scopes, created by owners and admins in the portal.
• application/problem+json errors carrying a stable code, and X-Request-Id on every response.