SMS Gateway · Web Tester

API —

Authentication

Username Password

JWT token (auto-filled after login, editable)

All requests below are sent with Authorization: Bearer <token> when a token is present.

POST /sms/single

Sender Recipient

Telegram → recipient = chat id · WhatsApp → recipient = phone number. Pick the channel below.

Message

Channel

Priority (1–5)

POST /sms/templated

Sender Recipient (phone) Message template Placeholders (JSON)

Template ID

Channel

POST /sms/tasked

Sender Recipient (phone) Message Schedule mode Scheduled At (ISO, for Timed) Schedule Config (JSON)

Channel

Priority

POST /sms/group

Sender Contact Group ID Message Placeholders (JSON, optional)

Channel

Priority

POST /sms/list (multipart)

Sender Message Contact list file (CSV/Excel)

Channel

Priority

GET /queues/stats

Live depth of queues 1–5 and a status summary.

GET /sms (list & lookup)

Status filter

Page size

GET /audit

Table filter

Page size

📊 Dashboard · GET /dashboard/stats

Days

POST /sms/templated/list (multipart)

Sender Template ID Message template CSV file (Recipient,value1,value2,…)

Channel

Priority

POST /sms/tasked/template

Sender Recipient (phone) Message template Placeholders (JSON)

Schedule mode

Channel

Scheduled At (ISO, for Timed) Schedule Config (JSON)

POST /sms/tasked/list (multipart)

Sender Message Contact list file (CSV)

Schedule mode

Channel

Scheduled At (ISO, for Timed) Schedule Config (JSON)

GET /settings · POST/PUT

Setting ID (edit)

Key Value

Category Description

Active Encrypt value

GET /whatsapp/webhook · mimic Meta verification

Meta calls this URL when you click "Verify and save". The server echoes the challenge back only when the verify token matches the stored META_VERIFY_TOKEN. This panel reproduces that exact GET request (no Authorization header, like Meta). The verify token field may be left empty to test the rejection path (401).

hub.verify_token (may be empty)

hub.challenge