Wapito API reference

Every Wapito endpoint, grouped the way the OpenAPI document groups them. Each operation page carries its parameters, its request and response bodies with real examples, the webhooks it raises, the errors it can return and the same call written in twelve languages.

Base URL and authentication

https://api.wapito.com/v1

Send a channel token on every request: Authorization: Bearer wpt_YOUR_TOKEN

A token belongs to one channel — one linked WhatsApp number — so no request carries a channel id. Every error shares one envelope and is identified by a stable code; branch on that, never on the message.

99 endpoints in 11 groups

  • Channel

    The channel itself: connection status, health, quotas, settings, QR and pairing-code linking, the profile of the linked account, incoming calls and metered usage. Everything here is scoped to the single channel your token belongs to.

    11 endpoints

  • Chats

    The conversation list: read chats, mark them read or unread, archive them and delete them locally. Chat data comes from the engine store, so it reflects what the engine has observed since the channel connected.

    6 endpoints

  • Contacts

    Contacts known to the linked account, checking whether a number is registered on WhatsApp, and the phone-number to LID mapping that modern WhatsApp traffic increasingly depends on.

    8 endpoints

  • Groups

    Create groups, manage participants and admins, control the invite link and the four security settings, work the join-request queue and leave. Creating groups and adding participants are the highest ban-risk calls in the API.

    21 endpoints

  • Labels

    WhatsApp Business labels and their chat associations, plus the phase-2 business profile, catalog and orders surface. Labels require a WhatsApp Business account; personal numbers get `business_account_required`.

    7 endpoints

  • Media

    Upload files once and reuse them across sends, download the files Wapito copied out of inbound messages, and delete stored files. Signed links let you hand media to a browser without exposing your channel token.

    4 endpoints

  • Messages

    Send text, media, links, locations, contact cards and polls; read, edit, delete, forward, star and react to messages. Sends pass through the per-channel queue that spaces and jitters traffic to keep the number healthy.

    21 endpoints

  • Newsletters

    WhatsApp Channels, called newsletters at protocol level: create one, list and search them, read their posts and delete them. Posting is an ordinary send to a `@newsletter` recipient.

    8 endpoints

  • Presence

    Publish online, typing and recording indicators, subscribe to presence for a chat and read the last state observed. WhatsApp only streams presence for chats you explicitly subscribe to.

    5 endpoints

  • Stories

    Status updates: post text, image, video and voice statuses to selected contacts. Statuses expire after twenty-four hours and are only visible to people who have the number saved.

    3 endpoints

  • Webhooks

    Manage webhook subscriptions and test them, and the reference for every event Wapito delivers. Deliveries are signed with HMAC-SHA256, retried with backoff and documented under the `webhooks` section of this specification.

    5 endpoints

The OpenAPI document

The whole contract is published as one OpenAPI 3.1 document. Import it into Postman or Insomnia, generate a client with your own toolchain, or read it in the browser — the interactive reference is the same document with a request runner attached.

Related

Try it on your own number

Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.