Introduction
Learn the core concepts for managing WhatsApp sessions in Sendable.
Documentation Index
Browse the full docs navigation at
/docsbefore diving into session-specific workflows. Use it to quickly jump between setup, API keys, webhooks, and troubleshooting.
Managing Sessions
View and control all connected WhatsApp sessions from the Sendable Dashboard.
Warning: If a session fails to connect, review troubleshooting guidance at
/docs/troubleshooting.
Creating a session
A session is a single connected WhatsApp account in Sendable.
Each session has:
- Its own phone number and connection state
- Its own API keys
- Independent message history and webhook activity
- A designated city for proxy configuration
Select a city first
Before creating a session, you must select a city. This determines the residential proxy configuration used for the connection.
Sendable supports 164 cities worldwide across all continents. When creating a session, you'll choose from cities including:
- Medan, Bandung, Surabaya (Indonesia)
- Bangkok (Thailand)
- Singapore
- Mumbai, New Delhi (India)
- London (UK)
- New York, Los Angeles (USA)
- São Paulo (Brazil)
- Lagos (Nigeria)
And many more. See the Cities page for full details.
Important: City selection is permanent. Once a session is created, the city cannot be changed. To use a different city, create a new session.
Create the session
- Open Dashboard
- Click New Session
- Select a city from the dropdown (164 cities available)
- Name the session (for example:
Support-Jakarta-Prod) - Scan the QR code from WhatsApp Linked Devices
- Wait for status to become Connected
Session states
| State | Description | Action |
|---|---|---|
connecting | Setup in progress | Wait for QR scan |
connected | Ready for message traffic | No action needed |
disconnected | Connection lost | Reconnect and check phone network |
expired | QR code timed out | Generate a new QR code |
Managing session details
From each session detail page you can:
- Rename the session
- Generate or revoke API keys
- Configure webhook endpoints
- Monitor health and recent activity
- Stop or delete the session
Regional setup
For location-based operations, create dedicated sessions per city and route traffic accordingly.
See the city strategy guide at Cities.
Best practices
- Select city before creating the session (this is required)
- Use clear names by use case and location
- Keep the source phone online and stable
- Separate development and production sessions
- Monitor connection health daily