Text

The simplest messages are made of text. Text messages are best suited to communicate information without the need for visuals, complex interaction, or response.

✅ Supported Features

Plain text up to 2,000 characters (varies by carrier)

Basic line breaks (\n)

Unicode character support

Delivery and read receipts (if enabled by user)

Fallback to SMS if RCS is unavailable (optional)Media and PDF files

When you send a message with an image, video, audio, or PDF file, your agent must provide a publicly accessible URL for the content or directly upload the file. For media files, you can also specify a thumbnail image that lets users preview the content before clicking on it. For audio files, the default audio widget is used as a placeholder.

Example

The following code sends a plain text message. For formatting and value options, see phones.agentMessages.create.

Request

Header Params

Authorization

string

required

Example:

Bearer <ACCESS_TOKEN>

Content-Type

string

required

Example:

application/json

Body Params application/json

string

required

agentID

string

required

message

object

required

templateId

string

required

Examples

Noraml Text MessageText with variables

{
    "to": "<MOBILE>",
    "agentID": "<AGENT_ID>",
    "message": {
        "templateId": "<TEMPLATE_ID>"
    }
}

Responses

🟢200Success

application/json

Body

message

string

required

data

array [object {3}]

required

messageId

string

optional

mobile

string

optional

charges

number

optional

Example

{
    "message": "1 numbers accepted",
    "data": [
        {
            "messageId": "a8XXXXXX-1bXX-4XXd-b5XX-5dXXXXXX:1",
            "mobile": "+9198XXXXXXXXX",
            "charges": 0.05
        }
    ]
}

🟠400Bad Request

🟠401Unauthorized

✅ Supported Features#

Example#

Request

Responses

✅ Supported Features

Example