Routing & control
Advanced sender rotation
When your key is pool-mode and the request carries no sender hint, the rotation engine picks a healthy sender. Strategy + weight are configured per-number in the dashboard.
Strategies
| Strategy | How it works | Best for |
|---|---|---|
round_robin | Cycles through healthy numbers in order. Distribution is very even. | Steady traffic, all numbers equally seasoned. |
least_used | Picks the sender with the lowest message count in the current period. Self-balances during bursts. | Bursty traffic / promo broadcasts. |
random | Uniform random over healthy numbers. Non-deterministic. | A/B routing tests or deliberately unpredictable distribution. |
weighted | Per-number weight (1–100). Proportional to total weight of the healthy pool. | Mix of old + new numbers — give low weight to new ones until they're warm. |
Automatic health filter
Before the strategy runs, the engine filters:
- Status must be active or idle (banned / disconnected are skipped).
- Numbers pinned to another active API key are excluded from the pool (they're reserved for that key).
- Priority (-100 to 100) acts as a tiebreaker.
Configure in the dashboard
- Open the Numbers / Rotation page.
- Pick the strategy for the chosen number.
- Set weight (when weighted) and priority as needed.
{
"strategy": "weighted",
"weight": 25,
"priority": 10,
"enabled": true
}