WhatsApp sessions
Each session has its own connection, queue and history. Copy its ID for API requests.
Your profile
Your usage
Account renewal
Your saved WhatsApp credentials and message history are preserved. An administrator must approve renewal by setting a new expiry date.
Platform overview
Session support
Support actions require confirmation and are recorded in the audit log.
User management
Click approve, choose an expiry date, then Save expiry and approve account. Renewal requests appear in the Expiry / Renewal column.
| User | Role / status | Sessions | Expiry / Renewal | Actions |
|---|
Platform limits
Audit log
Your gateway, in view.
A live look at your connection and messaging activity.
WhatsApp connection
LINKED DEVICEChecking connection…
Your linked phone number will appear here.
Manage session →Instance details
- Connected number
- —
- Last connection
- —
- Server uptime
- —
- Daily counts timezone
- —
Recent messages
View history →| Direction | Phone | Message | Status | Time |
|---|
No messages recorded yet. Your next message will appear here.
WhatsApp Session
Manage your connection without losing your saved session.
Link your WhatsApp
WhatsApp → Settings or ⋮ → Linked Devices → Link a Device
QR codes refresh automatically. Keep this page open.
Checking connection…
Session details
- Phone number
- —
- Last connected
- —
- Session first recorded
- —
- Connection state
- —
Temporary disconnect keeps authentication and stays paused across server restarts.
Remove WhatsApp Session
Remove this linked session and require a new QR scan. Message history and API keys stay available.
Send Message
Send text, an image or a PDF to a recipient expecting your message.
A small, deliberate send.
Messages sent here use the same connection, validation and rate limits as your API.
- Messages are queued immediately and sent one at a time, even after a restart.
- Only one send can be in progress.
- Check your phone before retrying an uncertain send.
Messages
Incoming and outgoing messages, with the status reported by WhatsApp.
| Direction | Phone | Message | Type | Status | Date / Time | Details |
|---|
No messages match your search.
Message Queue
Pending messages survive restarts. Pausing allows an in-progress send to finish.
| Direction | Phone | Message | Type | Status | Date / Time | Attempts | Next attempt | Details |
|---|
No messages match.
API Keys
Give your local applications secure access to the send API.
Your API keys
HASHED + ENCRYPTED| Name | Key | Scopes | Created | Last used | Status | Action |
|---|
No database keys yet. Create one for your application.
New keys can be revealed only by their authenticated owner. Older hash-only keys cannot be recovered. Revocation takes effect immediately. All active keys and recent revoked keys are shown, up to 100 entries.
Webhooks
Connect your application to incoming messages and gateway events.
| Name / URL | Events | Enabled | Last delivery | Success / Failed | Created | Actions |
|---|
No webhook endpoints yet.
Webhook Deliveries
Receivers must deduplicate event IDs. Retries may deliver an event more than once.
| Event ID / Event | Endpoint | Status | Attempts | HTTP | Created | Last attempt | Delivered | Error / Actions |
|---|
No deliveries match.
Settings
Conservative sending limits, shared across the dashboard and API.