Number verification DCQL Request

Use this method to generate a credential request structure for the Android CredentialManager for the SIM-based (TS.43) number verification use case. The response must be passed to the device for SIM-based (TS.43) authentication.

post/camara/number-verification/v2/dcql/verify

Request

Base URL
https://api.infobip.com (the document declares no server; this is the origin it was published from)
Auth
- OAuth 2
  Client credentials
  Token URL: https://api.infobip.com/auth/1/oauth2/token
- or API key in header Authorization
- or API key in header Authorization
- or HTTP basic

Request body

noncestring required

A single-use, client generated value. The client keeps it and uses it to correlate the eventual response. Infobip embeds this same value in the credential_authorization_jwt payload.

carrierIdsinteger[] required

Array of Android canonical carrier IDs.

Example request

{
  "nonce": "2307e608-e619-4df5-a460-a99b4446f3f0",
  "carrierIds": [
    123,
    456
  ]
}

Response

OK — per-carrier map of DCQL credential objects or error objects

C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeDcqlResponseDto required

Map of resolved DCQL credential objects keyed by carrier ID, used to build the credential request structure for the Android CredentialManager (TS.43 SIM-based authentication). If one or more requested carriers could not be resolved, their error responses will be returned in the same map. For unresolved carrier response structure, see DCQL Carrier Error Map section.

C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeDcqlNotFoundErrorResponse required

Map of DCQL error responses keyed by carrier ID, returned when one or more requested carriers could not be resolved. Resolved carriers will be returned in the same map. For resolved carrier response structure, see DCQL Credential Map section.

Changes

No recorded changes to this operation across all 1 revision of this API.