Number Verification API

Overview

The Number Verification API confirms whether a phone number provided by the service provider matches the phone number of the device/SIM on the mobile network.

• Version: 1.0.0
• Base URL: https://api.pxg.konera.com/camara
• Path: /number-verification/v1/verify
• OpenAPI: number-verification.json

Typical use cases

• Passwordless login / OTP replacement – Verify number ownership without SMS OTP interception risk.
• Account binding – Ensure a user is actually using the phone number they claim during registration.
• High‑risk actions – Re‑verify number ownership before enabling sensitive features (limits increase, device binding, etc.).

Security

• OAuth2 Client Credentials
  • Token URL: https://auth.konera.com/oauth2/token
  • Scope: number-verification.read – Verify device phone number match

Headers

• x-correlation-id (optional, string) – Correlation ID for request tracing.

Request

POST https://api.pxg.konera.com/camara/number-verification/v1/verify

Body schema: NumberVerificationRequest

{
  "phoneNumber": "+123456789"
}

• phoneNumber (string, required) – MSISDN in E.164 format entered by the end user.

Responses

200 – Number verification result

Body schema: NumberVerificationResponse

{
  "devicePhoneNumberVerified": true,
  "assessedAt": "2026-02-05T10:30:00Z"
}

• devicePhoneNumberVerified (boolean) – true if the number matches the device/SIM on the network.
• assessedAt (string, date-time, nullable) – Time when verification was performed.

HTTP status codes

Standard Error payload with:

• 200 OK – Verification completed.
• 400 Bad Request – Invalid request body or missing required fields.
• 401 Unauthorized – Invalid/missing token.
• 403 Forbidden – Caller not allowed to use this verification API.
• 429 Too Many Requests – Rate limit exceeded.
• 500 Internal Server Error – Unexpected server error.