--- title: "Get KYC Review by ID (V1)" method: GET path: "/v1/profiles/{profileId}/kyc-reviews/{kycReviewId}" tags: ["kyc-review"] deprecated: true --- # Get KYC Review by ID (V1) `GET /v1/profiles/{profileId}/kyc-reviews/{kycReviewId}` > **Deprecated.** {% admonition type="warning" %} This endpoint is deprecated. Use [Get KYC Review by ID](kycreviewget) (V2) instead. {% /admonition %} Retrieves a single KYC Review by ID for a profile. ## Path parameters - `profileId` integer, required - `kycReviewId` string, uuid, required ## Headers - `X-External-Correlation-Id` string, uuid ## Response `200` Returns the KYC Review object. - KycReview — The return object of most KYC Review endpoints, which includes information about the given KYC Review such as status, trigger references, and a list of [KYC Requirements](api-reference/kyc-review/kyc-requirement). - `id` string, uuid — Unique identifier for a KYC Review resource, generated by Wise. - `status` 'NEW' | 'PASSED' | 'PASSED_WITH_REQUIREMENTS' | 'WAITING_CUSTOMER_INPUT' | 'PROCESSING' — Aggregated state of the underlying requirement set. Any of the states below could move into any other state. - `createdAt` string, date-time — Timestamp marking the creation of the KYC Review. - `updatedAt` string, date-time — Timestamp marking the last update of the KYC Review. - `requiredBy` string, date-time, nullable — Timestamp by which the underlying requirement set needs to be verified to not block the customer. Only relevant if the status is `PASSED_WITH_REQUIREMENTS`. - `triggerReferences` object[] — List of trigger reference objects. - `type` string — Type of the underlying action or process this KYC Review is for. Usually a reference to which product this KYC Review pertains to (like `QUOTE` or `TRANSFER`) or a reference to a KYC process on the profile that isn't related to a specific product (like `REFRESH_CYCLE` or `REPAPERING`). Currently supported types: - `QUOTE` - `TRANSFER` - `PROACTIVE_SEND_MONEY` - `ADD_MONEY` - `CARD` - `BANK_ACCOUNT_DETAILS` - `INFO_REQUEST` - `triggerData` object — Key-value object containing metadata of the underlying product object that triggered the KYC Review. For `QUOTE`, `TRANSFER` and `ADD_MONEY` types, `triggerData` contains an `id` field that refers to their respective IDs. For `BANK_ACCOUNT_DETAILS`, `triggerData` has a field called `currencies` which contains a list of currencies (e.g. USD, SGD, EUR) that the bank details have been created for. Fields and their data types for each `triggerReference.type`: - `QUOTE` - `id` (uuid) - `TRANSFER` - `id` (long) - `ADD_MONEY` - `id` (long) - `BANK_ACCOUNT_DETAILS` - `currencies` (list of string) - `redirectUrl` string, nullable — URL where the user will be redirected at the end of the flow. Can contain query params and path fragments. It has to be a valid URL as per [RFC 2396](https://www.ietf.org/rfc/rfc2396.txt). Provided by the caller in the [Update redirect URL](kycreviewredirecturlupdate) call. - `requirements` array[], nullable — Nested list of [KYC Requirement](api-reference/kyc-review/kyc-requirement) objects in `[[Requirement]]` format, where each inner list represents a combination of possible requirements to be provided. To fulfil the whole KYC Review, at least one item from each inner list should be provided. For example, if the requirements are `[[a, b], [c, d]]` then it should be read as `(a or b) and (c or d)`. - KycRequirement[] - `key` string — The name of the KYC requirement. A single KYC Requirement should appear in the requirements list at most once. - `state` 'NOT_PROVIDED' | 'IN_REVIEW' | 'VERIFIED' — The state of the KYC requirement. - `NOT_PROVIDED` — the information is pending. Either the Hosted KYC flow or [KYC Requirement Submit](/api-reference/kyc-review/kycreviewrequirementsubmit) endpoint should be used to fulfil the requirement. - `IN_REVIEW` — the required information has been retrieved and the KYC requirement is being reviewed. No action is needed. - `VERIFIED` — the required information has been received and verified on our side. No action is needed. - `apiCollectionSupported` boolean — Indicates if the requirement can be provided via the [KYC Requirement Submit](/api-reference/kyc-review/kycreviewrequirementsubmit) endpoint. If `false`, the requirement should be provided via the Hosted KYC flow. - `additionalRequirements` object[], nullable — List of additional submissions that are needed to fulfill this requirement. These can appear when the originally submitted evidence is a wrong document, wrong format, incomplete or otherwise insufficient. Only provided if not empty. - `additionalRequirementId` string, uuid — Unique identifier for an additional requirement, generated by Wise. - `key` 'ACKNOWLEDGEMENT,' | 'DOCUMENT' | 'WRITTEN_ANSWER' | 'DOCUMENT_AND_WRITTEN_ANSWER' | 'DOCUMENT_OR_WRITTEN_ANSWER' | 'EMAIL' | 'CUSTOM_REQUEST' — A key outlining what type of evidence is additionally required - `state` 'NOT_PROVIDED' | 'IN_REVIEW' | 'VERIFIED' — The state of the additional requirement. This state should be treated as independent of the parent KYC Requirement's state. They can, but don't have to, change together. - `NOT_PROVIDED` — the information is pending. Either the Hosted KYC flow or [KYC Requirement Submit](/api-reference/kyc-review/kycreviewrequirementsubmit) endpoint should be used to fulfil the additional requirement. - `IN_REVIEW` — the required information has been retrieved and the additional requirement is being reviewed. No action is needed. - `VERIFIED` — the required information has been received and verified on our side. No action is needed. - `reasons` object — Contains information about the reason this additional requirement has been requested. - `errorCode` 'NEEDED' | 'WRONG_DOCUMENT' | 'EXPIRED' | 'INVALID_TRADING_ADDRESS' | 'MISSING_ONE_SIDE' | 'MISSING_COUNTRY_OF_RESIDENCE' | 'MISSING_DIRECTORS' | 'MISSING_UBOS' | 'NO_UBO_DOC_REQUIRED' | 'MISMATCH_NAME' | 'MISMATCH_DATE_OF_BIRTH' | 'AGENT_DETAILS_PROVIDED' | 'DIRECTOR_IS_BUSINESS' | 'UBO_IS_BUSINESS' | 'UNCLEAR' | 'WEBSITE_LINK_BROKEN' | 'BUSINESS_NAME_NOT_ON_WEBSITE' | 'DRIVING_LICENSE_NOT_ACCEPTED' | 'BUSINESS_NOT_REGISTERED' | 'OTHER' — Code for the reason this additional requirement has been requested. - `description` string - `dateTime` string, date-time — Timestamp marking when this additional requirement was requested. - `attributes` object — Contains metadata information about the additional requirement. Not returned if empty. - `fields` object — Not returned if empty - `name` string — The name of the affected person(s) or business - `website` string — The URL of the affected website - `businessName` string — The name of the affected business - `owningBusinessName` string — The name of the affected owning business - `markdownText` string — Free format text written by a Wise Agent in markdown format. - `issues` string[] — A list of issues with the previously uploaded document. Not returned if empty - `versions` object[] — **Conditional:** Only present when `apiCollectionSupported` is `true`. Lists the available versions and their validity. - `version` string — The version identifier. - `validUntil` string, date, nullable — If present, indicates the expiry date of this version (ISO 8601). - `attributes` object, nullable — **Conditional:** Only present for certain requirement types that provide additional contextual information. The keys within this object vary depending on the parent requirement `key`. See the [KYC requirement types](/guides/product/kyc/wise-kyc/kyc-requirement-types) guide for details on which requirement types support attributes and what keys they contain. ## Other responses - `401` — User is not authorised to access the resource. - `404` — KYC Review not found. - `429` — Rate limit exceeded. Retry after the number of seconds specified in the `Retry-After` header. --- [API](https://skmtc.net/wise/apis/platform-api.md) · [All operations](https://skmtc.net/wise/apis/platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wise/platform-api/revisions/4907a1d269ab/schema)