Changelog
API v1 version tracking, compatibility promise, deprecation policy and changelog.
Version Policy#
The Bokko Public API follows semantic versioning. The current stable version is: v1.
- Major change (v1 → v2): non-backwards compatible — separate URL prefix, temporary parallel execution.
- Minor change (v1.0 → v1.1): backwards compatible expansion (e.g., new optional field, new endpoint).
- Patch: bug fix, internal change, the contract does not change.
What is the Contract#
The following constitute part of the API contract — integrators can rely on these:
- Endpoint URL and HTTP method.
- Names and types of request and response fields (for required fields).
- Error code values, their HTTP status and
retryableflags. - Capability names and their scope.
- Webhook event names and the value of the
payload.eventfield.
What is NOT part of the Contract#
We do not guarantee stability for the following:
- Adding or removing optional fields (if they were not
requiredpreviously). - Error message text (
messagefield) — only thecodeis stable. Metaextension fields (meta.truncated,meta.returnedSlots, etc.).- Rate limit quota values (the structure is stable, the values are not).
- Internal Firestore paths, Cloud Function names.
Current v1 Contract Summary#
| Contract dimenzió | Darabszám |
|---|---|
| Dokumentált endpoint | 14 |
| Stabil error code | 27 |
| Webhook event | 8 |
| Capability | 8 |
| Rate limit group | 5 |
Deprecation Policy#
If an endpoint, field, or capability is phased out:
- We communicate the deprecation at least 6 months in advance.
- Affected endpoints receive a
DeprecationHTTP response header (RFC 8594). - The planned shutdown date is indicated by the
SunsetHTTP response header. - Email notification to the Pro subscriber's registered contact email.
Tipp
There is currently no active deprecation. If the first deprecation occurs, the activation of backend headers and the email pipeline will be part of the deprecation event. The above policy is a communication promise, not a description of already deployed infrastructure.
v1.0.0 — 2026-05-05 — Initial Publication#
The first stable public release. The numbers below apply to this release and remain fixed — they do not update automatically if the contract expands.
- 14 documented endpoints
- 27 stable error codes
- 8 webhook events
- 8 capabilities
- 5 rate limit groups
Endpoints:
POST /availability/searchGET /bookingsPOST /bookingsGET /bookings/{bookingId}POST /bookings/{bookingId}/cancelGET /bookings/{bookingId}/eventsGET /servicesGET /staffGET /subscriptionGET /webhooks/configPUT /webhooks/configDELETE /webhooks/configPOST /webhooks/config/rotate-secretGET /webhooks/deliveries