Create a template

post

https://api.sintalk.com.br/v3/templates

Create a message template. content is read against the schema channel selects: text for sms, a file_id reference for voice, and for rcs one of the three shapes identified by their fields — text (text), card (card), or carousel (cards). Every file content references must already be uploaded and of a kind the slot accepts.

The {{variable}} placeholders found in content are extracted into variables; each send then supplies a value for every one of them, per recipient. name is unique per channel among live templates. Content, channel, and follow-up rules are fixed at creation — only name can be changed afterwards.

Body Params

A message template to create. content is read against the schema channel selects, and every file the content references must already be uploaded and of a kind the slot accepts. The {{variable}} placeholders found in content are extracted into the template's variables. Only name can be changed afterwards.

name

string

required

length between 3 and 120

Template name, 3 to 120 characters. Unique per channel among live templates.

channel

string

enum

required

Channel this template is sent over. Selects the accepted content shape.

Allowed:

content

required

Channel-specific content, read against the schema channel selects.

SMS
Voice
RCS

follow_up_rules

array of objects

Rules that send another template when a send of this one reaches a given outcome; at most one rule per outcome.

follow_up_rules

Responses

201The template as stored, with the variables extracted from its content.

400The request was rejected before it was applied — either a field failed validation (validation_failed, with error.fields naming each one), or the request could not be read at all (bad_request: malformed JSON, an unknown field, a missing parameter, or an unparseable path or query value).

401No credential was presented, or the one presented was rejected.

403The credential is valid but is not allowed to call this operation.

404No resource with that id exists in your account. An id belonging to another account is reported the same way as one that never existed.

409The request collides with what already exists, or with the resource's current state. Re-read the resource before retrying.

422The body parsed and every field is individually valid, but the request cannot be applied as asked. Retrying it unchanged will fail again.

429Rate limit exceeded

defaultAn unexpected error. Safe to retry with backoff; use an idempotency key where the operation accepts one.