Meowsapp WhatsApp API
Documentation menu

Start here

Guides

API reference

More

Start here

Introduction

Meowsapp WhatsApp API lets you connect a WhatsApp number you already own to your software in minutes, and then talk to it like any other REST API.

What it is

The service runs the WhatsApp Web multi-device protocol on your behalf. You link a phone number by scanning a QR code (exactly like WhatsApp Web), and from then on that number is a session you address by a clientId you choose. Sending is aPOST; receiving is a webhook. The platform keeps the session connected, reconnects it after restarts, and routes every request to the machine holding the connection — you never see any of that.

  • No Meta Business verification, no message templates, no per-conversation fees. It is your number, driven by API.
  • Every message type WhatsApp supports between people: text, replies, mentions, all media, voice notes, stickers, polls, buttons, reactions, edits, deletes, locations, contact cards, and groups.
  • One token for your whole account, with optional per-session secrets you can hand to your own customers.

Unofficial channel — read the fair-use page

This is not the WhatsApp Business (Cloud) API. It is subject to WhatsApp's terms for linked devices, and bulk or unsolicited messaging can get a number banned. See Limits & fair use before building outreach flows.

How it fits your system

Three moving parts, all HTTPS:

  1. Your app → API. https://api.meowsapp.com with Authorization: Bearer <token>. Start sessions, send messages, manage groups, read hosted history.
  2. API → your webhook. One POST per inbound event to the webhookUrl you registered, signed with a bearer token you chose. Retried on failure.
  3. Your webhook → API (optional). A poll-option lookup we call to resolve poll votes to names.

Bring your own store, or hosted inbox

You decide where conversation history lives:

Recommended for products

Bring your own store

Point webhookUrl at your server. Every event (with media descriptors) lands in your database; sends go out via the API. You own the data model. Nothing is stored on our side except the session itself.

Fastest to ship

Hosted inbox

Set a workspace id and point webhookUrl at the hosted receiver. We store every message in and out, copy media to permanent public links, resolve profile pictures, and expose GET /chatrooms and friends. Read it from any client.

Both modes can be combined: hosted history for your inbox UI, plus your own webhook for automations, by forwarding events from your receiver to ours.

Where to go next

  • Quickstart — token, pair, send, receive. Ten minutes.
  • Core concepts — clientId, LIDs vs phone numbers, chat room ids, message ids, pods.
  • Receiving messages — the receiver contract, every event type, retries and idempotency.
  • API reference — every endpoint with samples.