Get KYC Profile
GET/api/accounts/:accountId/kyc-profile
Get a KYC profile by account id if it exists.
Request
Path Parameters
Id of the cardholder or identity account.
Query Parameters
Include personal details (name, date of birth, etc) in the response. Requires additional permissions.
Responses
- 200
- 403
- application/json
- Schema
- Example (from schema)
Schema
The KYC profile id.
The account id.
Possible values: [created
, pending
, passing
, passed
, failing
, failed
]
The status of the KYC profile.
Region code.
Timestamp of KYC profile creation.
The Immersve Resource Name (IRN) that created the resource.
Timestamp of this KYC profile modification.
The Immersve Resource Name (IRN) that modified the resource.
{
"id": "afd4772562be47f8a3467a11d06c96ba",
"accountId": "225d85e65495722bf6517ea0ba0d6f56",
"status": "created",
"region": "NZ",
"createdAt": "2022-11-16T03:13:18.142Z",
"createdBy": "irn:314d85e65495722bf6517ea0ba0d4lp3:api-key:SLOs3U38hdhfEqwF1JKpTw",
"modifiedAt": "2022-11-16T03:13:18.142Z",
"modifiedBy": "irn:314d85e65495722bf6517ea0ba0d4lp3:api-key:SLOs3U38hdhfEqwF1JKpTw"
}
Subject is not allowed to perform the action with the reason stated in the errorCode
FORBIDDEN Account does not exist or there are no sufficient permissions to view KYC profile for this account.
KYC_PROFILE_DOES_NOT_EXIST KYC profile does not exist for this account. It gets created upon initiating the first KYC check.
LIVENESS_MISMATCH Resource liveness does not match request liveness.
- application/json
- Schema
- Example (from schema)
Schema
{
"statusCode": 403,
"statusName": "Forbidden",
"errorCode": "FORBIDDEN",
"reason": "Unauthorized"
}