WhatsApp Messaging API by Retention Stack
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHATSAPP_API_KEY | Yes | Your RapidAPI key. The server exits on startup if it is missing. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List all WhatsApp sessions belonging to this API key. |
| create_sessionA | Create a new WhatsApp session. Returns a session name and STARTING status — pair it with get_qr_code next. |
| get_session_statusA | Get the current status of a session (STARTING, SCAN_QR_CODE, WORKING, FAILED, STOPPED). |
| get_qr_codeA | Get the QR code to authenticate a session by scanning with WhatsApp (Settings > Linked Devices). |
| request_pairing_codeA | Request an 8-digit pairing code as an alternative to scanning a QR code. |
| check_contact_existsA | Check whether a phone number is registered on WhatsApp before sending to it. |
| send_text_messageA | Send a WhatsApp text message to a contact, group, or channel. |
| send_imageB | Send an image to a contact, group, or channel via a public URL. |
| send_fileB | Send a file (PDF, document, etc.) to a contact, group, or channel via a public URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct actions: session creation/auth vs. sending messages vs. contact checks. There is slight overlap between list_sessions and get_session_status, since list_sessions may reveal statuses too, but the descriptions keep them reasonably separated.
All tool names follow a clear lowercase snake_case verb_noun pattern: list_sessions, create_session, get_qr_code, send_text_message, etc. The naming is predictable and consistent across the set.
Nine tools is well-scoped for a WhatsApp messaging API: session lifecycle management, authentication, contact validation, and message sending. Each tool serves a clear purpose without excessive redundancy.
The core workflow is covered: create and authenticate sessions, check contacts, and send text/image/file messages. Minor gaps exist such as no delete/stop session tool and no video/audio sending, but the essential use cases are supported.