Message
HTTP Basic Authentication. Encode username:password in Base64 and pass as:
Authorization: Basic <base64_encoded_credentials>
Use your eCall account credentials or a dedicated API sub-user created in the eCall portal (Interfaces → Overview).
Request body for sending a single message. Use either to (single recipient)
or toList (multiple recipients) — not both.
The messaging channel to use.
| Value | Description |
|---|---|
Sms | SMS (also automatically routes to Pager or Voice for landline numbers if configured) |
Whatsapp | WhatsApp Business messaging |
Rcs | Rich Communication Services |
SmsPossible values: Sender address.
- SMS: Up to 16 numeric characters or up to 11 alphanumeric characters (ASCII 32–126). Test sender values carefully — not all providers accept all alphanumeric characters. Free accounts may only use the registered mobile number.
- WhatsApp: Phone number of the registered WhatsApp Business Account in
international format (e.g.
0041769999999). Contact eCall support to set up. - RCS: Your RCS sender ID as assigned by the provider. Contact eCall support to register and obtain the sender ID.
0041769999999Single recipient address in international format (e.g. 0041781234567 or
+41781234567). Mutually exclusive with toList.
+41781234567Scheduled send time in ISO 8601 format. If omitted, the message is sent immediately.
2025-12-20T10:00:00ZMessage content. For SMS, WhatsApp, and RCS, use TextContent.
Message accepted successfully.
The request is invalid. This may be caused by a missing required parameter,
an invalid value, or a constraint violation. Check the errorCode and
errorDetails in the response body for specifics.
The Authorization header is missing or the credentials are invalid.
Verify your username, password, and Base64 encoding.
An unexpected error occurred on the eCall server. Retry after a short delay.
If the problem persists, contact eCall support and include the x-f24-request-id
header value from the response.
HTTP Basic Authentication. Encode username:password in Base64 and pass as:
Authorization: Basic <base64_encoded_credentials>
Use your eCall account credentials or a dedicated API sub-user created in the eCall portal (Interfaces → Overview).
Unique message identifier as returned in the send response.
97031dc9-3814-4178-a31c-1599aa83ba67Status retrieved successfully.
The request is invalid. This may be caused by a missing required parameter,
an invalid value, or a constraint violation. Check the errorCode and
errorDetails in the response body for specifics.
The Authorization header is missing or the credentials are invalid.
Verify your username, password, and Base64 encoding.
The requested resource (message ID, media ID, etc.) was not found.
An unexpected error occurred on the eCall server. Retry after a short delay.
If the problem persists, contact eCall support and include the x-f24-request-id
header value from the response.
Last updated
Was this helpful?
