Medibill Gateway — Enterprise WhatsApp SMS Console

Medibill Gateway Multi-Device v2.0

WhatsApp Devices

0 / 0

Online WhatsApp phone sessions

Client Accounts

0

Configured user accounts

Messages Delivered

0

Successful transmissions

Gateway Uptime

0m

Continuous service uptime

Pending Client Approvals

0 Pending

Clinic / Client	Linked WhatsApp Phone	Paired At	Assign Message Quota	Decision
Loading pending approvals...

Users & Linked WhatsApp Devices

User Account	Connected WhatsApp	Device State	API Secret Key	Quota (Used / Cap)	Actions
Loading users and device sessions...

API Test Sandbox

Live Interactive Tester

Anti-Ban Protection Active

Single messages send instantly (0s). Bulk / rapid bursts automatically paced with 4–8s randomized jitter.

Dispatching User / WhatsApp Account

Device: Checking...

Recipient Phone Number Country code + number without symbols (e.g. 91 for India).

Message / Caption Content 0 chars

Media Attachment URL (Optional) Direct public URL to a PDF, image, or invoice to deliver via WhatsApp.

Custom Attachment Filename (Optional)

Live cURL Snippet

curl -X POST "http://localhost:3000/api/send" ...

200 OK --:--:--

Recent Outbox Dispatches

Time	Dispatching User	Recipient	Message & Media	Delivery Status	Anti-Ban Pacing
No outbox dispatches recorded.

0. External Platform QR Pairing (POST /api/connect/session)

Integrate self-serve QR pairing into your website, clinic portal, or SaaS app. Request a 15-minute temporary pairing session:

curl -X POST "http://localhost:3000/api/connect/session" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Apollo Clinic Indiranagar",
    "redirectUrl": "https://yourportal.com/billing?status=linked"
  }'

Returns: { "connectUrl": "http://localhost:3000/connect?token=otk_...", "expiresAt": ... }

Redirect your user to connectUrl (or embed in an iframe). Once scanned, the account is held in Pending Approval until approved by the Medibill Administrator.

1. Standard JSON Dispatch (POST /api/send)

Pass the recipient, message body, and user API key in the header:

curl -X POST "http://localhost:3000/api/send" \
  -H "Content-Type: application/json" \
  -H "x-api-key: USER_API_KEY" \
  -d '{
    "to": "918555993595",
    "message": "Your prescription order #MB-902 is verified."
  }'

2. HTTP GET Endpoint (SMS Gateway Compatible)

Simple URL query trigger for legacy software and SMS gateways:

GET http://localhost:3000/api/send?key=USER_API_KEY&to=918555993595&msg=Your+OTP+is+491024

3. Bulk Broadcast with Anti-Ban Pacing (POST /api/send-bulk)

Submit multiple recipients in one call. Medibill Gateway enqueues the batch and injects 4s–8s randomized jitter between consecutive dispatches so your account is never flagged or banned:

curl -X POST "http://localhost:3000/api/send-bulk" \
  -H "Content-Type: application/json" \
  -H "x-api-key: USER_API_KEY" \
  -d '{
    "recipients": ["918555993595", "919876543210"],
    "message": "Your clinic appointment is confirmed for tomorrow at 10:00 AM."
  }'

Parameter Compatibility & Aliases

Parameter	Supported Aliases	Notes
Recipient	`to`, `number`, `phone`, `mobile`	Country code + number without symbols (e.g. `918555993595`)
Message Body	`message`, `msg`, `text`	UTF-8 text message
API Key	`x-api-key` Header, `Authorization: Bearer <key>`, or `?key=` query	User secret key token (`vg_live_...`)

Success Response (200 OK)

{
  "success": true,
  "message": "WhatsApp message sent successfully",
  "data": {
    "messageId": "3EB023A94CEE4A5CF960C6",
    "recipient": "918555993595",
    "user": "Dr. Sharma Clinic",
    "userId": "usr_a1b2c3d4",
    "remainingQuota": 986,
    "timestamp": "2026-09-18T14:34:09.870Z"
  }
}