KYC Age Verification API
Overview
The KYC Age Verification API checks whether the subscriber associated with a phone number is at least a specified minimum age.
- Version: 0.2.0
- Base URL:
https://api.pxg.konera.com/camara - Path:
/kyc-age-verification/v0.2/verify - OpenAPI:
kyc-age-verification.json
Typical use cases
- Age-gated services – Enforce age thresholds for services such as gambling, alcohol delivery, or adult content.
- Regulatory compliance – Satisfy local regulations that require proof of legal age for specific digital services.
- Risk and fraud controls – Use age as an additional input to risk scoring during onboarding or high‑risk actions.
Security
- OAuth2 Client Credentials
- Token URL:
https://auth.konera.com/oauth2/token - Scope:
kyc-age-verification.read– Verify minimum age for a subscriber
- Token URL:
Headers
x-correlation-id(optional, string) – Correlation ID for request tracing.
Request
POST https://api.pxg.konera.com/camara/kyc-age-verification/v0.2/verify
Body schema: KycAgeVerificationRequest
{
"phoneNumber": "+14155550123",
"minimumAge": 18
}
Fields
phoneNumber(string, required) – MSISDN in E.164 format.minimumAge(integer, required) – Minimum age in years that the subscriber must meet or exceed.
Responses
200 – Age verification result
Body schema: KycAgeVerificationResponse
{
"ageVerified": true,
"assessedAt": "2026-02-10T10:00:00Z"
}
ageVerified(boolean) –trueif the subscriber is at least the requested minimum age.assessedAt(string, date-time, nullable) – Time when the age verification was performed.
HTTP status codes
All error responses use the common Error schema (status, code, message).
- 200 OK – Age verification completed successfully.
- 400 Bad Request – Invalid request body or missing required fields (e.g., malformed phone number or
minimumAge). - 401 Unauthorized – Invalid or missing access token.
- 403 Forbidden – Caller not allowed to use the KYC Age Verification API.
- 429 Too Many Requests – Rate limit exceeded.
- 500 Internal Server Error – Unexpected server error.