Introduction

The Wahide REST API provides programmatic access to WhatsApp Multi-Device features, allowing you to send messages, manage device connections, handle incoming webhooks, and orchestrate campaigns.

API Architecture & Standards

The Wahide API is organized around RESTful principles. All requests are communicated over HTTPS using standard HTTP verbs (GET, POST, PUT, DELETE) and expect/return UTF-8 encoded JSON payloads. All endpoints require authentication using a Bearer token or API key in the request headers.
API Base URL
Active API Base URL: `https://api-wa.hidessh.com` All endpoint paths documented in this reference are relative to this root URL. In local development or staging, this dynamically adapts from `NEXT_PUBLIC_API_BASE_URL`.

Phone Number Formatting

All phone numbers must follow the international E.164 standard without spaces, dashes, parentheses, or a leading plus sign (+) or zero. For example, an Indonesian number 0812-3456-7890 should be formatted as: `6281234567890`
Country Code Required
Always include the country dial code (e.g. 62 for Indonesia, 1 for United States, 60 for Malaysia). Requests with invalid formats will return an HTTP 400 response.

Quickstart

You can test your API connectivity by dispatching a test message via cURL. Replace `YOUR_API_KEY` with your secret key from the dashboard settings:
cURL Quickstart
curl -X POST "https://api-wa.hidessh.com/wa/messages/send" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "628123456789",
    "message": "Hello, your order #INV-2026 has been confirmed."
  }'

Key Capabilities

• **Multi-Device Rotation**: Connect multiple WhatsApp phone numbers and distribute message loads automatically via round-robin pooling. • **Natural Delivery Dynamics**: Support for typing presence indicators and configurable jitter backoff. • **Dynamic Spintax**: Use syntax like {Hello|Hi|Greetings} to produce unique variations across bulk deliveries. • **Meta Cloud API Compatibility**: Drop-in endpoint compatibility (/api/v1/v18.0/{deviceId}/messages) for existing Meta integrations. • **Delivery Tracking**: Track real-time message states (PENDING, SENT, DELIVERED, READ, FAILED) through inbound webhook callbacks.