⚠️ Important: API V1 Deprecation Notice

[!IMPORTANT]
Attention Developers: API V1 is now in Limited Support Mode.
Current Capabilities: API V1 now only supports legacy Message Sending (Text, Image, File, Voice, Video, and Link Previews) and simple status/usage checks.
End of Life: API V1 will be completely discontinued on April 10, 2026.
You must migrate your projects to API V2 before this date to avoid service interruption.

Wawp API V2 — The Future of WhatsApp Integration 🚀

API V2 is a ground-up rebuild designed for speed, reliability, and advanced features. It provides full control over the WhatsApp lifecycle and introduces interactive messaging paradigms that were never possible in V1.

💎 Why Upgrade to V2?

V2 is not just an update; it's a massive expansion of what you can do with WhatsApp:

📱 Full Session & Auth Control

Lifecycle Management: Create, Start, Stop, and Restart instances via API.

Modern Auth: Real-time QR streaming (Raw/Image) and Phone Login (Request Code) support.

💬 Professional Messaging

Interactive Content: Send List Menus, Polls, and Events.

Rich Engagement: Support for Message Reactions and Status (Stories) updates.

Post-Send Control: Edit sent messages or Delete them for everyone.

👥 Groups & Channels

Group Automation: Create groups, manage participants (Add/Remove/Promote/Demote), and update settings.

Channel Control: Discovery, Following, and Muting WhatsApp Channels برمجياً.

🔔 Enterprise-Grade Webhooks

Real-time notifications for Incoming Messages, Reactions, Call Events, Presence Updates, and Group/Label changes.

🏗️ Technical Upgrade: Endpoint Structure

The most significant change is the move from a WordPress-dependent structure to a dedicated high-performance API subdomain.

Feature	Legacy API (V1)	Modern API (V2)
Base URL	`https://wawp.net/wp-json/awp/v1/`	`https://api.wawp.net/v2/`
Example Link	`.../awp/v1/sendImage`	`.../v2/send/text?`
Architecture	WordPress REST API Pipeline	Native Golang/Node.js High-Concurrency Engine
Auth Logic	Static Access Tokens	Dynamic Session-Based Bearer Auth

Legacy V1 Messaging (Deprecated)

While we prepare for the final shutdown, the following V1 endpoints remain active for basic sending:

Request Body (`/awp/v1/send`)

{
  "instance_id": "string",          // Your instance identifier
  "access_token": "string",         // API access token
  "chatId": "string",               // Recipient identifier
  "text": "Hello world!",           // Message text
  "file": {                         // Optional. Media payload
    "url": "https://example.com/photo.jpg"
  }
}

Chat ID Formats

Context	Example	Notes
User	`12132132131@c.us`	Phone number (E.164) without `+`, suffixed with `@c.us`.
Group	`12312312123133@g.us`	Group IDs end with `@g.us`.
Channel	`123123123@newsletter`	WhatsApp Channels (📰).

Migration Steps

Update Endpoint Domain: Change from wawp.net (legacy WP system) to our high-speed subdomain: api.wawp.net.

Update Endpoint Path: Replace all /wp-json/awp/v1/ paths with /v2/.

Update Authentication: Switch from static legacy tokens to dynamic, secure session-based Bearer authentication.

Implement Webhooks: Configure your servers to listen for events from webooks to ensure message delivery and tracking.

🤖 AI & MCP Integration (Smart Documentation)

At Wawp, we believe that documentation should be as smart as the code it describes. That's why we've implemented the Model Context Protocol (MCP), allowing you to connect our entire API documentation directly to your favorite AI development tools.

🚀 What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI models (like Claude, GPT-4, or those inside Cursor) to securely and reliably access external data sources. Instead of copying and pasting documentation, the AI can "ask" our server for the exact information it needs.

Explore Wawp AI-Ready (MCP) Documentation →

📂 Export Data

Download Wawp API in your preferred format for offline use or integration with other tools.

Open Export Dashboard →

OpenAPI Spec: Industry standard with full schemas, all response types, and authentication headers.

HTML / Swagger: Interactive Swagger UI documentation. Perfect for private teams or local testing.

Markdown: Detailed Markdown with request tables, response samples, and integration tips.

Raw JSON: Structured documentation in JSON format—best for building custom internal tools.

Generated: March 30, 2026

API V1

⚠️ Important: API V1 Deprecation Notice#

Wawp API V2 — The Future of WhatsApp Integration 🚀#

💎 Why Upgrade to V2?#

📱 Full Session & Auth Control#

💬 Professional Messaging#

👥 Groups & Channels#

🔔 Enterprise-Grade Webhooks#

🏗️ Technical Upgrade: Endpoint Structure#

Legacy V1 Messaging (Deprecated)#

Request Body (/awp/v1/send)#

Chat ID Formats#

Migration Steps#

🤖 AI & MCP Integration (Smart Documentation)#

🚀 What is MCP?#

📂 Export Data#