Skip to main content
POST
For a usage description of the Verification Service, please refer to the Verification page.

Endpoint

POST /phone-service/verification

Swagger

Authorizations

Authorization
string
header
required

Bearer token obtained from POST /auth. Valid for 60 minutes.

Body

application/json
method
enum<string>
required

The delivery method to use.

Available options:
sms,
email
Allowed value: "sms"
Example:

"email"

phoneNumber
string
required

Recipient's phone number in international format, no spaces or special characters. Required if method = sms.

Required string length: 6 - 20
Pattern: ^[0-9]+$
Example:

"436501234567"

email
string<email>

Recipient's email address. Required if method = email.

Example:

"test@test.com"

securityFactor
string

A custom numeric OTP (3–10 digits). If omitted, a 6-digit OTP is auto-generated.

Pattern: ^[0-9]{3,10}$
Example:

"123456"

externalId
string

Customer-defined transaction ID. Max length: 100 characters.

Maximum string length: 100
Example:

"12312"

messageTemplate
object

Optional template details for this verification.

voiceLang
string

Language code for OTP delivery (e.g., 'en-US'). Defaults to English if not provided.

Example:

"en-US"

Response

Successfully initiated verification.

status
boolean
required

Indicates whether the request was successful (true/false).

Example:

true

data
object
required