Automating SMS Verification: The XeroSMS API

Everything you can click in the dashboard, your software can call: order a number for a service and country, poll for the code, cancel and refund if nothing arrives. Teams use it for QA pipelines, onboarding flows and any process that verifies accounts at volume.

Getting access

1. Open API in the dashboard and request a key — approvals are quick, and the key draws on the same wallet as your dashboard.
2. Read the API docs page for the endpoint list and examples.
3. Keep the key server-side. It spends real money; treat it like a password.

The shape of an integration

1. Order: request a number for a service and country; the response carries the number and an order id.
2. Poll: check the order until the code field fills — every few seconds is plenty.
3. Timeout: if no code arrives before expiry, the order refunds itself; order again with another country.

Practices that save money

• Respect one order at a time per flow — burst-ordering ties up wallet balance in pending numbers.
• Route by success rate: the per-country rates on the dashboard hold true over the API.
• Log order ids; they reconcile one-to-one against your wallet history.