post
https://connect.routee.net/failover-otp/otp/send-failover
Send an OTP with a flow of steps (e.g. ViberOtp then Sms). Each step carries its own content.
Optional callback.url receives webhooks with the same JSON shape as tracking.
Response status: Succeeded (single-step flow), InProgress (multi-step — first channel accepted, failover may follow),
or Failed (no channel accepted). HTTP 200 is returned even when status is Failed.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
RESPONSE PARAMETERS
| KEY | DESCRIPTION |
|---|---|
| flowId | Flow UUID. Use for tracking (GET /otp/failover/{flowId}). Null when status is Failed. |
| status | InProgress (multi-step — first channel accepted), Succeeded (single-step), or Failed. |
| type | Viber or Sms — channel that succeeded. Null when Failed. |
| flow | Echo of request steps; the sent step includes trackingId (message token). |
| createdAt | ISO-8601 timestamp. |
| error | Present when status is Failed. |
| statusCode | When Failed: 0 server error, 1 insufficient balance, 2 no next step, 3 failover not triggered. |
401Invalid or expired Bearer token
403Missing Bearer credentials
422Request validation failed

