Failover
Overview
Failover lets you reach your audience over more than one channel in a single ordered flow — for example Viber first, then SMS or Voice if the message is not delivered within the time you set.
You define step order and failover conditions (e.g. move to the next channel when Viber returns Expired, Failed, or Undelivered). Routee starts the first step immediately and advances through the flow as your rules are met.
Routee exposes three send APIs for different message types (promotional Viber, transactional BM templates, and OTP). They are not interchangeable — pick the one that matches your content.
Start here: Failover endpoints — which API to use — full comparison, scenarios, and links to API reference.
Documentation map
| Topic | Page |
|---|---|
| Which endpoint should I use? | Failover endpoints — comparison & scenarios |
| Service overview & use cases | General |
| Send — standard (promotional / session Viber) | How to send a Failover message |
| Send — transactional Viber (BM templates) | How to send a transactional Failover message |
| Callbacks & webhooks | Callbacks (Webhook) |
| Status reference | Failover Statuses |
| All API endpoints | Resource Overview |
API reference (FAILOVER): Standard · Transactional · OTP send
Detailed Status
When the overall flow status is Failed, the statusCode field (string) gives more detail:
- "0" — Server/system error while sending the next step
- "1" — Insufficient balance when sending the next step
- "2" — Failover triggered but no next step was configured
- "3" — Terminal status was not in that step’s
failoverOnStatuses
See Failover Statuses for flow logic, per-channel statuses, and defaults.
Updated about 1 month ago