Version: 1.0.0
AgileTelecom RCS API
REST API for sending RCS (Rich Communication Services) messages. Supports text messages, rich cards, carousels, and interactive suggestions with fallback to WhatsApp and SMS.
Authentication
All requests require one of the following methods:
- API Key — Header
X-Api-Key: <api-key> - Basic Auth — Header
Authorization: Basic <base64(username:password)>
Key Features
- RCS message sending: text, rich cards, carousels
- Interactive suggestions (buttons, links, quick replies)
- Automatic fallback to WhatsApp and SMS
- Delivery, read, and inbound message notifications (webhook)
Webhooks
The following callbacks are sent via HTTP POST to your URL configured in the platform.
DELIVERY
{
"channel": "RCS",
"eventType": "DELIVERY",
"messageId": "uuid",
"destination": "+393401234567",
"statusCode": 3,
"description": "delivered",
"eventDate": "2025-10-16T10:42:18Z"
}
statusCode: 3 = delivered, 6 = undeliverable
READ
{
"channel": "RCS",
"eventType": "READ",
"messageId": "uuid",
"destination": "+393401234567",
"eventDate": "2025-10-16T10:43:00Z"
}
INBOUND
{
"channel": "RCS",
"eventType": "INBOUND",
"messageId": "msg-id",
"source": "+393471488489",
"destination": "+393209998877",
"receivedDate": "2025-10-31T10:59:05.099Z",
"messageType": "TEXT",
"text": "User reply message"
}
messageType: TEXT, IMAGE, AUDIO, VIDEO. For media, the mediaKey field contains the key for downloading via /api/files/{mediaKey}.
Authentication
- API Key: ApiKeyAuth
- HTTP: Basic Auth
API Key provided by AgileTelecom
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Api-Key |
Username/password credentials
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | basic |
Contact AgileTelecom: