Introduction Authentication Send Message Send Busy Send Tally Send Media Send Sticker Send Button Send List Send Poll Send Location Check Number Generate QR Device Management
WA-BUSY REST API

WhatsApp API
Built for Busy.

Connect your application, Busy ERP or business workflow with Wa-Busy using simple HTTP API endpoints. Send messages, documents, media and manage WhatsApp devices from your own software.

Base URL https://zone-a.wabusy.in

Authentication

API endpoints protected by the API middleware require a valid API key.

API Key Your unique authentication key.
Device The WhatsApp device identifier used by the request.
HTTP Requests can use GET or POST where supported.
Example 
api_key=YOUR_API_KEY
device=YOUR_DEVICE
Keep your API key private. Do not expose it inside public JavaScript, frontend source code or client-side applications.

Send Message

Send a text message to a WhatsApp number.

POST Send text message
/send-message
Parameter Type Required Description
api_key string Required API authentication key.
device string Required WhatsApp device identifier.
number string Required Recipient WhatsApp number.
message string Required Message content.
cURL 
curl -X POST "https://zone-a.wabusy.in/send-message" \
-d "api_key=YOUR_API_KEY" \
-d "device=YOUR_DEVICE" \
-d "number=919876543210" \
-d "message=Hello from Wa-Busy"

Send Busy

Send Busy-related documents or generated content through the dedicated Busy API endpoint.

POST Busy API
/send-busy
Parameter Type Required Description
api_key string Required API authentication key.
device string Required WhatsApp device.
number string Required Recipient number.
message string Optional Message or caption.

Send Tally

Tally integration endpoint for sending generated business documents through WhatsApp.

POST Tally Document API
/send-tally
This endpoint supports the Tally integration flow. Send the required Tally/XML payload according to your integration setup.
Endpoint 
POST https://zone-a.wabusy.in/send-tally

Send Media

Send documents, images, videos and supported media through WhatsApp.

POST Media
/send-media
Parameter Type Required Description
api_key string Required API key.
device string Required WhatsApp device.
number string Required Recipient number.
media_type string Required Type of media.
url string Required Public media URL.
caption string Optional Media caption.
cURL 
curl -X POST "https://zone-a.wabusy.in/send-media" \
-d "api_key=YOUR_API_KEY" \
-d "device=YOUR_DEVICE" \
-d "number=919876543210" \
-d "media_type=document" \
-d "url=https://example.com/file.pdf" \
-d "caption=Your document"

Messaging Features

Additional WhatsApp message formats available through the API.

POST Send Sticker
/send-sticker
POST Send Button
/send-button
POST Send Product
/send-product
POST Send List
/send-list
POST Send Poll
/send-poll
POST Send Location
/send-location
POST Send VCard
/send-vcard

Check Number

Check a WhatsApp number through the API.

POST Check Number
/check-number
cURL 
curl -X POST "https://zone-a.wabusy.in/check-number" \
-d "api_key=YOUR_API_KEY" \
-d "device=YOUR_DEVICE" \
-d "number=919876543210"

Generate QR

Generate or retrieve the QR connection information for a WhatsApp device.

GET Generate QR
/generate-qr
Parameter Type Required Description
api_key string Required API authentication key.
device string Required Device identifier.
force boolean Optional Force device creation/initialization when supported by the API flow.
Request 
GET https://zone-a.wabusy.in/generate-qr
    ?api_key=YOUR_API_KEY
    &device=YOUR_DEVICE
Example response 
{
    "status": true,
    "message": "QR generated successfully"
}

Device Management

Manage WhatsApp devices connected to your account.

POST Logout Device
/logout-device
POST Delete Device
/delete-device

User & Device Information

Public user and device information endpoints.

POST Create User
/create-user
POST Info User
/info-user
POST Info Devices
/info-devices

Response Handling

Always inspect the returned status and message before treating a request as successful.

JSON 
{
    "status": true,
    "message": "Request processed successfully",
    "data": {}
}
Response fields can vary depending on the endpoint. Always handle both successful and failed API responses in your application.