Skip to main content
GET
cURL
Use the request_id returned when you started the verification. Authenticate with an API key belonging to the same application. A pending verification has not established the person’s identity. Check the final outcome before using the returned identity as verified data. Wallet-specific attributes vary by wallet and country. For a phone approval, use Poll wallet verification to advance the authentication check. For the complete integration sequence, see Digital ID wallet APIs.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Path Parameters

request_id
string<uuid>
required

The request_id the start endpoint returned.

Response

One standalone wallet verification, as every wallet endpoint answers it.

request_id
string<uuid>
required
wallet_verification
object
required
vendor_data
string | null
required
metadata
object | null
required

The metadata object sent at start, or null.

created_at
string<date-time>
required