Key Takeaways
- Multi-device failover means remaining paired Androids can still claim jobs when one phone drops — not a hidden SMPP cluster.
- Live field names live in Developer Center. Typical shape: send JSON plus optional device ids.
- Do not invent a priority-failover endpoint. Route OTP to a dedicated pool in your adapter.
- One radio with two SIMs is not two devices. Device count is handsets.
- You bring phones and operator credit. Platform pricing is devices plus send volume.
Failover is more phones, not a magic flag
API usage for multi-device failover is boring on purpose: pair more than one Android, keep them online, send with routing your adapter understands. Feature: dual SIM and multi-device. Live parameters: Developer Center— this page will not mirror fields that can change.
Pricing meters devices and send volume. Two SIMs in one chassis still count as one device. You fund every operator.
What the send call actually does
HTTPS POST with Bearer token and JSON { to, text }. Optional routing ids assign the batch. If you omit them, you get default routing. Confirm names and types in Developer Center before you ship.
“If your adapter hardcodes one device UUID from staging, production failover is a comment in a ticket, not a feature.”
Samples: PHP, C#— REST, not a failover SDK.
Routing patterns
| Pattern | When | Watch for |
|---|---|---|
| Omit device ids | Single primary / default pool | Primary down ⇒ queue waits |
| Pass a set of device ids | Split a batch / pin a pool | Stale ids after you retire a phone |
| OTP adapter → OTP pool only | Login must not sit behind bulk | Shared helper that “helpfully” uses all devices |
| Canary device id | Staff numbers | Canary SIM empty |
What automatic failover is not
It is not SMPP network failover. It is not dual-SIM slot fallback unless you coded slot selection. It is not “Twilio-like geo routing.” If device A is offline, jobs that require A wait. Jobs that can use B need B paired and allowed by your send call.
Webhooks: DLR. Page on device offline and queue age, not on vibes.
Ops that make API usage work
- Spare charged, paired, same app version.
- Config maps purpose → device set; no literals in five services.
- Setup: pairing.
- OTP isolation: OTP.
Plans: pricing. Device caps are the failover budget.
Next steps
Pair two phones, kill one, watch the other claim staff canaries, then encode the device set in config — not in tribal memory.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- multi-device and dual SIM routingCapacity and failover
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
