Send RCS Template Message

Available for accounts in India.

Send an approved RCS template to a customer. RCS templates are created and approved inside the Splashify Pro dashboard — each has a unique template_id (a UUID) that you reference here.

Note: RCS must be approved on your account and the template must be in the approved state.

Approval means the carrier has finished reviewing your RCS registration. While that review is still open your account shows as Processing, and this endpoint returns 403 with code: "rcs_kyc_not_approved". That is deliberate: an integration that starts working before the sender is approved keeps working right up until it does not, and the failure lands in production rather than in testing.

You can still send test messages from the dashboard during the review, and those are free. See RCS Templates.

Endpoint

POST

https://api.splashifypro.com/api/v1/public/rcs/send

This is the one RCS endpoint, and it sends approved templates only. There is no separate template URL to call, and no free-form option: a request without a template_id is rejected with 400 and code: "template_required".

Templates are how RCS traffic is meant to be sent. The carrier reviews and approves each one, which is what lets it be delivered as branded, verified messaging rather than being filtered.

Headers

Header	Value
`Authorization`	`Basic YOUR_API_KEY`
`Content-Type`	`application/json`

Request body

{
  "to": "+919876543210",
  "template_id": "bbd644a9-502a-11f1-a6c3-7e338e7c5434",
  "variables": ["Rahul", "A-1042"]
}

Field	Required	Notes
`to`	yes	Recipient phone number in E.164 format (e.g. `+919876543210`)
`template_id`	yes	UUID of an approved RCS template from your dashboard
`variables`	if the template has any	Values for the template's variables. See Template variables

Template variables

RCS templates use numbered variables: {{1}}, {{2}}, up to {{10}}. Older templates written with {#var1#} work the same way: {#var1#} is {{1}}. Nothing is filled in for you, so send a value for every variable the template uses.

variables can be sent in either of two forms:

Form	Example	Fills
A list	`["Rahul", "A-1042"]`	`{{1}}`, `{{2}}` in order
An object keyed by number	`{"1": "Rahul", "2": "A-1042"}`	Each variable by its number

A template with this message text:

Hi {{1}}, your order {{2}} has shipped.

sent with "variables": ["Rahul", "A-1042"] is delivered as:

Hi Rahul, your order A-1042 has shipped.

Variables are filled in the message text, card titles and descriptions, button labels, and at the end of a button link. A value in a link is encoded for a web address: A 1/2 becomes A%201%2F2 in the path, and after a ? it is encoded as a query value.

If a value is missing or makes a field too long, the request is refused with 400 and nothing is sent or charged:

{
  "success": false,
  "code": "missing_variables",
  "missing": ["{{2}}"],
  "message": "This template needs a value for {{2}}. Send them in 'variables'."
}

`code`	When
`missing_variables`	A variable has no value, or an empty one. `missing` lists each one
`variable_too_long`	A filled field is over its limit: message text 2000 characters, card title 200, card description 2000, button label 25
`invalid_variables`	`variables` is not a list or an object, an object key is not a number from `1` to `10`, or the template has a variable in the middle of a link

The older POST /api/v1/public/rcs/send-template endpoint is deprecated. It fills variables the same way but takes a list only.

Example

curl -X POST https://api.splashifypro.com/api/v1/public/rcs/send \
  -H "Authorization: Basic YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+919876543210",
    "template_id": "bbd644a9-502a-11f1-a6c3-7e338e7c5434",
    "variables": {"1": "Rahul", "2": "A-1042"}
  }'

Successful response — `200 OK`

{
  "success": true,
  "rcs_message_id": "a1b2c3d4-...",
  "message_id": "d58aeff7-a81c-47a7-9b67-f381e13f6c4e",
  "conversation_id": "ee64970d-0539-4eb0-859d-2147859a604d"
}

Field	Notes
`rcs_message_id`	The provider message id — correlates with delivery webhooks
`message_id`	Your Splashify Pro message id
`conversation_id`	The RCS conversation this message belongs to

Opt-outs

Anyone you message can reply STOP to stop hearing from you. When they do, we record it, reply to confirm it, and refuse every later send to that number with 403 and code: "recipient_opted_out". Broadcasts skip them too, and you are not charged for a message that is not sent.

Treat that 403 as final rather than retrying it. The person can start receiving messages again themselves by replying START, and only they can.

You choose the words that count as STOP and START, and the replies we send back, in Settings → Opt management. Keep STOP in the list: the carrier requires it, and an agent that ignores it can lose its approval.

Errors

Status	Meaning
`400`	`to` and `template_id` are required, or `template_id` is not a valid UUID. A request with no `template_id` returns `code: "template_required"`
`400`	A variable is missing (`missing_variables`), a filled field is too long (`variable_too_long`), or `variables` is malformed (`invalid_variables`). See Template variables
`401`	Missing or invalid API key
`402`	Insufficient wallet balance
`403`	RCS is not enabled for your account, or its carrier approval is still pending (`code: "rcs_kyc_not_approved"`)
`403`	The recipient has opted out of messages from your business (`code: "recipient_opted_out"`)
`403`	The template is not approved yet (`code: "template_not_approved"`)
`404`	Template not found
`429`	Rate limit exceeded
`502`	The RCS provider rejected the message

{
  "success": false,
  "message": "Template not found"
}