Skip to main content
POST
/
v1
/
api
/
verify
Verify a mobile number
curl --request POST \
  --url http://service.authmatech.com/v1/api/verify \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --header 'X-CLIENT-ID: <x-client-id>' \
  --data '
{
  "mobileNumber": "<string>",
  "encryptedMobileNumber": "<string>",
  "operatorId": "<string>",
  "serviceType": "<string>",
  "sdkSessionId": "<string>"
}
'
{
  "success": true,
  "messages": [
    {
      "type": "SUCCESS",
      "httpStatus": "OK",
      "technical": false
    }
  ],
  "data": {
    "validNumber": true
  }
}
Confirms that a customer controls the mobile number they present, using the encrypted proof (encryptedMobileNumber) and operatorId produced by the Authmatech SDK. Returns data.validNumber. Add ?maskMobile=true to also receive a masked copy of the confirmed number. Send both auth headers (X-API-KEY, X-CLIENT-ID). For the full flow and edge cases, see the Verify guide. A validNumber: false is a successful 200 with a negative verdict — see Errors.

Authorizations

​
X-API-KEY
string
header
required

Headers

​
X-CLIENT-ID
string
required

Query Parameters

​
maskMobile
boolean
default:false

If true, the response returns the Mobile Number in masked form (e.g. ******12). to help the customer in his verification journey

Body

application/json
​
mobileNumber
string
​
encryptedMobileNumber
string
​
operatorId
string
​
serviceType
string
​
sdkSessionId
string

Optional SDK session ID returned by the Authmatech mobile SDK after Header Enrichment. When present, the verification record is linked to the stored SDK session and device context.

Response

Verification successful