Total Clients0
Dashboard
Welcome back. Monitor clients, devices, and API delivery.
Welcome to LeadX WABA
Operate multi-client WhatsApp devices, API keys, and delivery activity from one console.
Total Devices0
Connected0
Messages0
Device Health
0%
Delivery Analytics
API & OTP Summary
Recent Activity
Connected Numbers
Manage DevicesClients
| Client | Status | Token Prefix | Created | Action |
|---|
Add Device
Devices
| Device | Client | Number | Status | Updated | Action |
|---|
Send Message
Recent Messages
| Time | Client | Device | To | Status | Message | Action |
|---|
Message Reports
Client Number Summary
| Client | Connected Number | Status | Total Sent | Text | Media | Media Breakup | Failed | Last Sent |
|---|
OTP Module
WhatsApp OTP Verification
Generate short-lived OTP codes for client login, lead verification, payment confirmation, or any app flow where the user must prove ownership of a WhatsApp number.
How it works
1. Select client
2. Send OTP on WhatsApp
3. User enters code
4. Verify from client app
OTP should be used only when the user requests it. Keep expiry short, do not share OTP in logs, and never ask users to forward OTP messages. Codes are saved as secure hashes, not plain text.
Send OTP
Verify OTP
Recent OTPs
| Time | Client | Number | Purpose | Status | Attempts | Expires |
|---|
Developer Documentation
LeadX WABA REST API
Share this guide with clients who need to connect a WhatsApp number by QR, check connection status, and send messages from their own website, CRM, app, or automation system.
Base URL
https://leadxwaba.in/api
This QR engine uses WhatsApp Web sessions. Use only opt-in contacts, avoid spam, keep message rate low, and do not share client access tokens publicly. If WhatsApp logs out a device, scan QR again from Devices.
AUTH
Authentication
Every client request must include the generated client access token shared by the LeadX WABA admin.
Header Option 1
Authorization: Bearer wa_leadx_CLIENT_TOKENHeader Option 2
X-Access-Token: wa_leadx_CLIENT_TOKENFull token is shown only when a client is created or when admin clicks Share New Token. Keep it private and use your backend as a proxy when possible.
QR
Device Pairing API
Use this flow when your website needs a QR scanner to connect a new WhatsApp number. After QR scan, the device appears in the LeadX WABA admin panel.
1. Get client access token from admin
2. POST /api/device/create
3. Show /api/device/qr-image
4. Poll /api/device/status
QR codes expire quickly. Reconnect preserves the saved session by default; request a forced new QR only when pairing is actually required.
POST
/api/send
Send a text message. Pass instance_id when the client has multiple connected WhatsApp numbers.
POST
Media, Document, Audio, Buttons
Use the same endpoint with different type and variables payload.
OTP
OTP Send & Verify
Client applications can trigger OTP directly and verify the received code.
1. Client calls /api/otp/send
2. LeadX WABA sends OTP on WhatsApp
3. User enters OTP in client app
4. Client calls /api/otp/verify
ERR
Error Responses
Use these responses to show clean messages in your client panel.
401Missing or invalid client token.
404No connected device found.
429Rate limit reached.
400Invalid payload, OTP expired, or wrong OTP.
SAFE
Best Practices
Recommended rules for stable delivery and lower account risk.
- Send only to users who requested communication or OTP.
- Keep OTP expiry short, normally 3 to 5 minutes.
- Do not store OTP code in your client app logs.
- Use a dedicated WhatsApp number for transactional OTP and alerts.
- Monitor failed messages and reconnect device when status changes.
Production Setup
Application Settings
Configure public API URL, documentation defaults, OTP policy, and support details before moving this engine to production.
Use HTTPS public URL in production, rotate admin password/JWT secret from .env, keep database credentials private, and never expose client access tokens in frontend code.