API Changelog
The Voka public API is stable. Breaking changes go through a /v2 path with a 6-month deprecation window on /v1.
We add fields to responses and webhook payloads without warning — those are non-breaking changes per our forward-compatibility contract. Consumers must ignore unknown JSON fields.
v1 — initial public release
| Date | Change |
|---|---|
| 2026-05-12 | Clarified X-Voka-Timestamp is Unix seconds (10-digit), not ISO-8601 — code samples updated to parse with parseInt / int(). The HMAC base string contract is unchanged; only the docs were ambiguous. |
| 2026-05-12 | DELETE /api/v1/webhook-subscriptions/{id} now supports the RESTful path-param form (legacy ?id= query-param still works). |
| 2026-05-10 | GET /api/v1/auth/whoami connection-test endpoint |
| 2026-05-10 | GET /api/v1/calls unified inbound + outbound list with cursor + page pagination |
| 2026-05-10 | GET /api/v1/calls/{id} call detail |
| 2026-05-10 | GET /api/v1/calls/{id}/transcript on-demand transcript pull with cache |
| 2026-05-10 | call.transcript.ready webhook event now fires reliably (was previously unwired) |
| 2026-05-10 | RFC 9457 problem-details error envelope with stable code extension |
| 2026-05-10 | Per-API-key rate-limit bucket added alongside per-customer bucket |
| 2026-05-10 | Retry-After header on every 429 |
| 2026-05-10 | Make.com ?challenge= verification probe handler |
| Earlier | GET /api/v1/assistants |
| Earlier | POST /api/v1/outbound-calls + GET /api/v1/outbound-calls/{id}/transcript |
| Earlier | POST / GET / DELETE /api/v1/webhook-subscriptions |
| Earlier | call.completed and call.insight.received webhook events |
Upcoming
| Target | Change |
|---|---|
| v1.1 | POST /api/v1/sms/send action |
| v1.1 | sms.received and sms.sent webhook events |
Versioning policy
- Additive changes (new fields, new endpoints, new event types): no version bump, no notice. Consumers ignore unknown fields per the contract.
- Behavior changes that aren't field renames (e.g. tighter rate limits, new validation rule): announced 30 days in advance via this changelog and customer email.
- Breaking changes (renames, removals, semantic changes): new
/v2path. The/v1path stays available for at least 6 months after/v2is announced. Both run in parallel during the deprecation window.
How to subscribe to changes
This page is the source of truth. RSS feed and email digest are on the roadmap.
For now, monitor the page or follow docs.vokaai.com for updates. Email support@vokaai.com to be added to the API change-notification list.