Send a transactional Failover Message

Same lifecycle as POST /failover, but Viber steps are template-only (BM transactional compliance).
Allowed step types: Sms, Viber (template), Voice. Free-form Viber message body and client
label are rejected with 400. Template fields on POST /failover are also rejected with 400.

Response includes flowKind: transactional and echoes template fields (including seq) on Viber steps.

JSON body: only flow (required) and optional callback. accountId and applicationId are not in the body;
they are set from integration headers.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

RESPONSE PARAMETERS


KEYDESCRIPTION
trackingIdThe tracking Id of the failover message.
flowKindAlways transactional for flows created with this endpoint. See Failover Callbacks.
typeThe type of the flow channel. Supported values: Sms, Viber, Voice.
fromThe sender id (SMS or Voice step).
toThe recipient number (SMS/Viber) or destination (Voice).
ttlTime (in minutes) until the message expires. SMS: integer, 1–1440 (default 1200). Viber: decimal (max one decimal place), 0.5–1440.0 (default 10). Voice steps do not use ttl.
orderThe order of the step in the failover sequence.
failoverOnStatusesArray of status strings that trigger the next channel. SMS: FAILED, UNDELIVERED (default: Undelivered, Failed). Viber: EXPIRED, FAILED, UNDELIVERED (default: Expired, Failed, Undelivered). Voice: Busy, NoAnswer (default). Case-insensitive.
messageSMS only. Details for the SMS message (body, flash, label, transcode, urlShortener).
bodyThe text of the SMS message.
flashIndicates if the message is a flash SMS.
labelThe label for the SMS message (max 350 characters). Not accepted on Viber steps for this endpoint.
transcodeIf true/false, the SMS body will/will not be transcoded. If omitted, the application-level setting is used.
dialPlansVoice only. Combination of action verbs to execute.
dialPlans.verbsArray of SAY and PLAY verbs. See possible values in the API reference.
senderInfoTrackingIdViber only. The unique sender id (e.g. from Routee Platform → Applications).
templateIdViber only — transactional. Approved Rakuten BM template UUID (echoed from request).
templateLangViber only — transactional. Template language code (e.g. en).
templateParamsViber only — transactional. Placeholder values object (echoed from request). OTP templates require pin.
deliveryScopeViber only — transactional. PRIMARY_DEVICE or ALL_DEVICES.
seqViber only — transactional. Sequence number; always present in create response (client value or generated).
inboundUrlViber only. Callback URL for inbound messages.
callbackCallback (webhook) configuration. See Callbacks (Webhook).
callback.strategyWhen the URL is called: on every status change (OnStep) or when a final status is reached (OnCompletion).
callback.urlURL to which the callback payload is posted.
createdAtWhen the flow was created (ISO 8601).

Transactional Viber steps do not use promotional fields such as message.text, imageUrl, action, or viberFile. Use templateId, templateLang, and templateParams instead. Sending free-form Viber content on this endpoint returns 400.

Body Params
flow
array of objects
required

Ordered list of failover steps. Viber steps must use BM template fields only (no free-form message). Sms and Voice steps match legacy Failover.

flow*
callback
object

Details about the callback, more information at Callbacks (Webhook)

Headers
string
required
Defaults to application/json
string
required
Defaults to Bearer {access_token}
Responses

400

Validation error or business rule failure (e.g. template on wrong endpoint, insufficient balance).

403

Forbidden — missing role or scope.

404

Unknown sender info or related resource not found.

Language
LoadingLoading…
Response
Choose an example:
application/json