Skip to content

    Arabic or English · ↑↓ to move · Enter to open · Esc to close

    العربية
    On this page

    Versioning

    How the API is versioned, what can change inside v2 and how to write clients that keep working.

    The major version is in the path: https://mursilat.com/api/v2/…. The current API version is 2026-10; webhook envelopes carry it as apiVersion.

    What can change inside v2

    • New endpoints, new optional request fields, new response fields.
    • New webhook event types (numbers subscribed to “all events” receive them automatically).
    • New error codes, and new values in status / reason enums.

    Write clients that ignore unknown fields and handle unknown event types and codes gracefully (log and move on). Anything that would break working code goes to a new version path — the way v2 was added next to v1, which keeps working unchanged.

    v1 (legacy)

    v1 (/api/v1/whatsapp/public/…, per-number x-api-key) keeps working. New features ship on v2. See Migrating from v1 to v2 and the v1 reference.