Skip to main content

OTP API

Verify a mobile number by SMS - send a one-time password, check it, and resend when it does not arrive.


Overview & Solution​

Mobile number verification sits at the front of almost every onboarding flow, and it is where a surprising share of drop-off happens: the code is slow, it never arrives, or there is no way to retry without starting over.

The OTP API covers the whole loop - send, verify, resend - with configurable code length and expiry, so verification fits your flow rather than the other way round.

Key Value Propositions​

  • Complete loop - send, verify and retry are all covered; no half-implemented resend.
  • Configurable - set code length and expiry per request to match your risk appetite.
  • Template support - send through your own approved SMS template so the message carries your brand.

Industry Use Cases​

1. Customer Onboarding & KYC​

  • Number verification at signup - confirm the applicant controls the number before creating an account.
  • Contactability check - catch mistyped numbers at the point of entry rather than at first collection call.

2. Field Operations​

  • Customer-present confirmation - have the field officer trigger an OTP to the customer's phone to evidence the visit actually happened with the customer there.
  • Delivery and handover - confirm the recipient at the doorstep.

3. Transaction & Approval Flows​

  • Step-up authentication - require a code before a sensitive change or approval.
  • Consent capture - record that the number holder agreed at a specific time.

How it works​

graph LR
A[Send OTP] --> B[Customer receives SMS]
B --> C{Code entered?}
C -->|Yes| D[Verify]
C -->|Not received| E[Resend]
E --> B
  1. Send - request a code for a mobile number, with your chosen length and expiry.
  2. Verify - submit the code the customer entered.
  3. Resend - trigger a retry through the selected channel if the first attempt did not land.

Works well with​

Pair it withTo get
Employee Management APIVerified numbers on workforce records
Custom Data Layers APIVerified numbers on your own customer records
Events APIA timestamped record that verification occurred