A complete developer reference for the Cloud SDK API, supporting secure and interoperable identity verification with Apple Wallet, Google Wallet, Samsung Wallet and State wallet.
Base URL: https://credenceid.com/cloudsdkdevBearer authJSONInteractive
01
Authentication
All API access begins with activation using a license key and profile ID. Use POST /v1/refresh to renew tokens before expiry.
Activate the verifier and obtain JWT tokens. Uses your license key and profile ID to establish an authenticated session. The Origin header must match the domain registered with your license.
JWT valid for 15 minutes. Use as Authorization: Bearer <token>.
refreshToken
Opaque token valid for 7 days. Use to renew the access token.
expiresIn
Access token TTL in seconds (900 = 15 min).
tokenType
Always "Bearer".
customerName
Configured customer name for the active license.
profileName
Human-readable profile name tied to the profile ID.
âšī¸
Implementation note
Call this from your backend. Treat the returned tokens as server-side credentials â never expose them to the client.
âšī¸
Chrome requirement for DC API flows
Apple Wallet and Google Wallet flows require Chrome 128+ with chrome://flags/#web-identity-digital-credentials enabled.
02
DC API â ISO 18013 (Apple Wallet)
Verify ISO standard mobile driver's licenses via the browser using Digital Credential (DC) API. For Apple Wallet on iOS
03
DC API â OpenID4VP (Google Wallet)
Verify ISO standard mobile driver's licenses via the browser Digital Credentials API using the OpenID4VP protocol. For Google Wallet on Android.
04
OpenID4VP mdoc Annex B (Samsung / CA DMV)
Verify ISO standard mobile driver's licenses using QR-code-based verification using ISO 18013-7 Annex B. Supports Samsung Wallet and CA DMV mDL wallets.
05
W3C OpenID4VP (State mDL)
QR-code-based flow using W3C OpenID4VP with did:web identity and direct_post response mode.
06
Wallet-Facing Endpoints
These endpoints are called automatically by wallets during the verification flow and must remain publicly reachable. If they are blocked by a firewall, private network policy, or ingress rule, the wallet cannot complete the flow.
07
Configuration
Retrieve profile configuration to confirm which document types and fields the verifier is set up to request.
Flow
Integration Flow Summary
plaintext
1. POST /v1/setup â get accessToken + refreshToken
2. POST /v1/refresh â renew accessToken before expiry
Per verification:
Apple Wallet: POST /v1/getDocRequest â navigator.credentials.get() â POST /v1/verifyDocRequest
Google Wallet: POST /dcapi/openid4vp/v1/initiate â navigator.credentials.get() â POST /dcapi/openid4vp/v1/validate
Annex B: POST /openid4vp/v1/mdoc/initiate â wallet calls GET /request + POST /response â GET /resume or poll POST /result
W3C (State): POST /w3c/openid4vp/v1/initiate â wallet calls GET /request + POST /callback â poll POST /validate