Skip to Content
Wapitick developers

Versioning and changelog

What can change in /v1, how deprecations are announced, and what changed.

  • /v1 only grows: new endpoints, new optional fields and new enum values are not breaking. Ignore fields you do not know and treat enums as open.
  • Breaking changes come as a new dated version or /v2. A deprecated endpoint answers with Deprecation and Sunset headers at least 6 months ahead (12 for fields that Zapier, Make, n8n, Slack or MCP integrations use).
  • Webhook payloads follow the api_version pinned on each endpoint.

Changelog

2026-11-20

  • Test mode: wk_test_ keys work in a separate test workspace with a sandbox WhatsApp number, magic numbers, test recipients and POST /v1/test/inbound.
  • Request log (GET /v1/request-logs), usage (GET /v1/api-usage), live event stream (GET /v1/events/stream).
  • api.requests.day is enforced; rate limits now hold across servers.
  • Webhooks: Standard Webhooks headers; every event type documented with its payload; new events for bookings, orders, payments, widget.chat_started and form.submitted.
  • OAuth client_credentials for confidential apps.
  • Website: one loader script for the WhatsApp button, chat, forms, booking and catalogue; platform detection; install checks; QR codes and a printable counter kit.
  • SDKs for Node, Python and PHP (Laravel), the wapitick CLI and a Postman collection.

This page as Markdown

On this page