Testing

Sandbox mode

Build and test your whole integration without sending a single real message or spending a cent.

Every account can create test API keys alongside its live ones. A test key runs the exact same endpoints, request shapes, and response shapes as live, with three differences: OTP send always returns the fixed code 123456 instead of generating and delivering a real one, no WhatsApp or Telegram message is ever sent, and nothing is charged to your balance.

cURL — sandbox

curl -X POST https://api.authevo.dev/v1/otp/send \
  -H "Authorization: Bearer sk_…" \
  -H "Content-Type: application/json" \
  -d '{ "phone": "+201234567890" }'

# → with a key created in test mode: always resolves with code 123456,
#   no real message sent, no charge

TOTP sandbox works differently, on purpose

Unlike OTP's fixed 123456, TOTP enroll in sandbox mode returns a fixed, public demo secret — add it to any real authenticator app and the codes you verify against it genuinely rotate every 30 seconds, just like production. There's no fixed TOTP code to hardcode in your tests.

Creating a test key

Create a test key from your dashboard's API keys page — it's issued instantly, no separate signup step. Test and live keys share the same account, credit balance display, and settings; only sending behavior differs.

Going live

Switch to your live secret key once you're ready to send real messages — no code changes beyond the key itself. Test-mode requests are never billed, so there's no cleanup needed before you switch.