API Reference Overview
The Tenreply REST API follows standard HTTP conventions. All endpoints require authentication via a JWT session (web app) or a trl_live_... API key.
Interactive reference
The full interactive API reference is available at:
https://api.tenreply.com/api/docsIt is auto-generated from the live backend and always reflects the latest version.
Key endpoint groups
| Group | Prefix | Description |
|---|---|---|
| Contacts | /api/contacts | Create, list, update, tag contacts |
| Conversations | /api/conversations | Start, close, assign conversations |
| Messages | /api/messages | Send text, media, and template messages |
| Templates | /api/templates | List and manage approved WhatsApp templates |
| Broadcasts | /api/broadcasts | Send campaigns to tagged contact lists |
| Webhook subscriptions | /api/webhooks/subscriptions | Register and manage REST Hooks |
| Zapier polling | /api/zapier | Polling endpoints for Zapier integration |
Response format
Successful responses return JSON. Errors follow:
{ "statusCode": 400, "message": "Validation failed", "error": "Bad Request"}Rate limits
The API enforces 100 requests per 60 seconds per API key. The Retry-After header indicates when to retry if you hit the limit.