Create a rich card RCS template

post

https://api.liguelead.com.br/v1/rcs/templates/card

Creates a single rich card with optional media and 1–4 interactive buttons (reply / open_url / dial_call). Sent as application/json. Provide media via either the public media_url or the base64 data URI media_file (or neither).

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

title

string

required

Friendly name persisted in the template registry.

header

string

required

length ≤ 100

body

string

required

length ≤ 1600

media_url

uri

Public URL of the media. Mutually exclusive with media_file.

media_file

file

Media file upload. Sent inline inside the JSON body as a base64 data URI (data:<mime>;base64,<payload>); the request is application/json, NOT multipart/form-data. The format: binary annotation is the trigger that makes the readme.io API Explorer (and Insomnia) render a file-attach widget that serialises the chosen file into this data URI shape on submit; the surrounding application/json content-type keeps SDK generators on the JSON code path. Mutually exclusive with media_url. Limit: 5 MB decoded.

fallback_message

string

length ≤ 306

default_variables

array of objects

Optional fallback values for the {{N}} placeholders inside body.

default_variables

buttons

array of objects

required

length between 1 and 4

1–4 interactive buttons.

buttons*

type

string

enum

required

Button variant. Drives which payload field is required (url for open_url, phone_number for dial_call; postback_data is optional and only used with reply).

Allowed:

title

string

required

length ≤ 25

Visible button label (max 25 chars).

url

uri

Required when type = open_url.

phone_number

string

Required when type = dial_call. E.164 format (e.g. +5511987654321).

postback_data

string

length ≤ 2048

Optional, only used when type = reply. Echoed back to your webhook when the user taps the button.

Responses

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Template created

422Validation or business-rule violation, e.g. url and file both supplied on the same card. Business-rule errors return { "error": "<message>" }; field-level validation errors return { "error": [{ "field": "...", "message": "..." }] }.