API Changelog
What changed in the API, newest first. Back to the reference
2026-07-19
- Auto top-up is now documented and available at two
scopes. Keep a shared account pool topped up
(
GET/PATCH /api/v1/accounts/{merchantId}/auto-topup) or protect a single app's balance (GET/PATCH /api/v1/apps/{appId}/auto-topup). Reads report whether a card is on file and which balance the setting governs. - Remove a per-app spending cap.
POST /api/v1/apps/{appId}/cap-removereturns an app's remaining cap balance to the shared pool and makes the app uncapped again — the inverse of cap top-up.
2026-07-17
- Manage your whole account by conversation. The admin assistant (Teach) can now create and configure apps, manage team members, buy credits, connect a calendar, and change plans — every money-spending or destructive action asks for explicit confirmation first.
2026-07-16
- Team lifecycle endpoints. Invite
(
POST /api/v1/users), change a role (PATCH /api/v1/users/{userId}), pause and resume sign-in (POST /api/v1/users/{userId}/pause), and remove a teammate (DELETE /api/v1/users/{userId}). Role changes are bounded by your own role. - Buy credits from your integration.
POST /api/v1/billing/topup-sessionreturns a hosted checkout link priced at your plan's per-minute rate. - Take an app offline.
POST /api/v1/apps/{appId}/unpublishremoves the published site without deleting the app. - List upcoming bookings.
GET /api/v1/apps/{appId}/bookingsreturns the operator view of appointments.
2026-07-15
- Web-chat components: render contract + curated
library. Saved actions can declare how their data renders in
chat (
cards,comparison,timeline), and you can pre-approve exact content that the assistant serves verbatim. - Scoped API keys. Self-mint hash-stored keys scoped to chat, knowledge or forms, and list or revoke them — see Scoped API Keys.
2026-07-13
- Buy a phone number from the API.
POST /api/v1/apps/{appId}/phone-numberpurchases and wires a number in one call, with automatic rollback if wiring fails;DELETEreleases it. - Automation rates are live. Workflow runs are billed per run plus per step-class; the launch rate table is published in the Workflow Execution section.