Skip to content
Back to blog
Guide

Switching your OTP provider to Authevo

By The Authevo Team5 min read

Most OTP integrations boil down to the same two calls regardless of who’s behind them: send a code to a phone number, then verify what the user typed back. Moving to Authevo means pointing those two calls at a new base URL and reading a slightly different response shape — not a rewrite.

What actually changes in your code

Two REST endpoints, plain HTTPS, no SDK required: POST /v1/otp/send with a phone number in E.164 format, and POST /v1/otp/verify with that phone number and the code the user entered. Both return a predictable { "data": {...} } / { "error": {...} } envelope. If your current provider uses the same two-call shape — most do — the change is a base URL, an Authorization: Bearer sk_... header, and a response-field mapping, not new business logic.

Start on our shared number — no WhatsApp setup required

The step that usually stalls a WhatsApp OTP migration is Meta Business Verification for a new WhatsApp Business Account — real, but not on your critical path here. New Authevo accounts send on Authevo’s own shared WhatsApp number immediately for Egypt and North Africa destinations, with automatic Telegram fallback from day one. You can finish the whole switch, in production, before touching Meta at all.

Bring your own WhatsApp number when you’re ready

Connecting your own WhatsApp Business Account is an upgrade you make on your own timeline, not a prerequisite — codes then send from your own branded number, and Meta bills you directly at cost. Business Verification for a brand-new Meta Business typically takes 48 hours to 14 business days; your documents go straight to Meta, never to us.

A checklist for the switch

  • Create an account and copy your sk_ secret key from the dashboard.
  • Create a test key and run your existing test suite against Authevo’s sandbox — fixed code, no real sends, no charge.
  • Swap the base URL and auth header, then map verified (and your error codes) onto whatever your app currently branches on.
  • Run a real end-to-end send on your live key to a phone you control before flipping production traffic over.
  • Cut traffic over, then decommission the old integration — no dual-write period required, since each request is independent.

What it costs, in the open

A flat $0.01 per successful verification, published, with a real per-market cost breakdown sourced to Meta’s own rate card — see the pricing page. Your first 50 verifications are free, so the checklist above costs nothing to run. Full parameter and error-code reference lives in the docs; sandbox details are on their own page.