Clicking through a web UI works for one verification — not for a hundred. QA teams testing signup flows, growth operators onboarding users at scale, and developers building OTP-dependent features all need the same thing: verification programmatically. That is what the AgoVerify API is for.
The programmatic flow
- Request a number — POST the service code and country; get back the number and an order reference.
- Poll or wait for webhook — the order status transitions to completed the moment the SMS lands, with the extracted code in the payload.
- Cancel when needed — expire an order and the balance release happens automatically.
Building it right
- Idempotency keys — retries must not double-order; key your requests.
- Webhook over polling — poll on a 10-15s interval as fallback, but let the webhook push codes to you when it is available.
- Per-country success metrics — log delivery per service+country; route your orders toward what actually works for your use case.
- Timeout discipline — cancel orders at your own deadline rather than letting them linger; the refund model means cancels are free.
Get your key
API keys are issued from the Developer page on your dashboard, with per-request pricing identical to web orders. Test in your own currency balance, measure delivery rates by route, and scale only the services that perform.
Ready to get verified?
Pick a service, top up once, and your code lands in seconds. Timed-out orders refund automatically.
Get your API key →