Developers
API Keys
API keys provide programmatic access to the Qwetty API. Manage them at Settings → API Keys.
Creating an API key
- Go to Settings → API Keys
- Click Create API Key
- Configure the key:
- Name — A descriptive name (e.g., "CRM Integration")
- Description — What the key is used for
- Permissions — Select which operations the key can perform
- Channel Scopes — Optionally restrict to specific channels
- IP Whitelist — Optionally restrict to specific IP addresses
- Expiration — Optionally set an expiration date
- Click Create
- Copy the key immediately — it will not be shown again
Managing keys
From the API Keys list, you can:
| Action | Description |
|---|---|
| View | See key details, permissions, and usage stats |
| Regenerate | Generate a new key value (invalidates the old one) |
| Revoke | Deactivate a key immediately |
| Reactivate | Re-enable a previously revoked key |
| Delete | Permanently remove a key |
Key status
| Status | Meaning |
|---|---|
| Active | Key is valid and accepting requests |
| Revoked | Key has been manually deactivated |
| Expired | Key has passed its expiration date |
| Expiring Soon | Key will expire within 7 days |
Permissions
API keys use granular permissions to control access. Only grant the permissions each integration needs:
- Read chats and messages
- Send messages
- Manage contacts
- Access templates
- Send template messages
Channel scopes
Restrict a key to specific channels. For example, a key scoped to your WhatsApp channel can only access chats and send messages through that channel.
Usage tracking
Each key tracks:
- Request count — Total API calls made with this key
- Last used — Timestamp of the most recent request
View usage stats at Settings → API Keys → [Your Key].
Rate limits
| Tier | Limit |
|---|---|
| Standard | 1,000 requests/hour |
| Admin | 5,000 requests/hour |
When you exceed the rate limit, the API returns 429 Too Many Requests.
Next steps
- Authentication — How API key auth works
- Send Your First Message — Use your key to send a message
- API Reference — Full endpoint documentation
Last modified on