Base URL
All API requests should be made to:Authentication
All API endpoints require authentication using a Bearer token. Include your API key in theAuthorization header:
Get your API key
Create and manage API keys in the Developer Portal
Request Format
- All requests must include
Content-Type: application/jsonheader - Request bodies should be valid JSON
- Phone numbers should be in international format without
+or spaces (e.g.,5511999999999)
Response Format
All responses are JSON objects with the following structure:Success Response
Error Response
HTTP Status Codes
| Status | Description |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid or missing API key |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource doesn’t exist |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error |
Rate Limits
Rate limits are applied per API key. Limits vary by plan:| Plan | Requests/Minute |
|---|---|
| Free | 500 |
| Starter | 2,000 |
| Pro | 10,000 |
| Enterprise | Custom |
API Endpoints
Messages
Send and manage WhatsApp messages
Instances
Manage WhatsApp connections
Webhooks
Receive real-time events
Inbound Webhooks
Send messages via webhook URLs
SDKs
We provide official SDKs for easier integration:Node.js
npm install @enviaai/sdk
Python
pip install enviaai
Java
Maven / Gradle
PHP
composer require enviaai/sdk
Versioning
The API is versioned using URL path (e.g.,/v1/). When we make breaking changes, we release a new version while maintaining support for older versions.
The current API version is v1. We’ll notify you via email before deprecating any version.
Support
Need help? Contact us:- Email: [email protected]
- Discord: discord.gg/enviaai
- GitHub: github.com/enviaai