How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wise kyc-review API

KYC Review API provides endpoints to view, update and submit information related to the KYC flow.There are two ways to collect KYC requirements from your customers:- **Hosted KYC** — redirect your customer to a Wise-hosted UI that guides them through the process.- **API submission** — use the [KYC Requirement Submit](/api-reference/kyc-review/kycreviewrequirementsubmit) endpoint to submit requirements directly. This is only available for requirement types where `apiCollectionSupported` is `true`.Please refer to our [Hosted KYC guide](/guides/product/kyc/wise-kyc/hosted-kyc) for more information on the general use of the endpoints included below.

Wise kyc-review API is one of 48 APIs that Wise publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include kyc-review. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 6 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0.

Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.

6 operations 4 paths 2 schemas 3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.wise.com/v2
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 4

Wise kyc-review API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (UserToken). It accepts HTTP bearer tokens (JWT) (PersonalToken). It accepts HTTP bearer tokens (JWT) (ClientCredentialsToken). It accepts HTTP basic authentication (BasicAuth).

  • UserToken — User Access Token for making API calls on behalf of a Wise user. Can be obtained via two OAuth 2.0 flows: - registrationcode grant: For partners creating users…
  • PersonalToken — Personal API Token for individual personal or small business users. Generated from Wise.com Settings Connect and manage apps API tokens. Has limited API access…
  • ClientCredentialsToken — Application-level token for partner operations that don't require a specific user context, such as bulk settlement and card spend controls. Obtained via POST /…
  • BasicAuth — Basic Authentication using your Client ID and Client Secret as the username and password. Client credentials are provided by Wise when your partnership begins.…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 3 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

kyc-review 6

KYC Review API provides endpoints to view, update and submit information related to the KYC flow. There are two ways to collect KYC requirements from your customers: - Hosted KYC…

POST
/v1/profiles/{profileId}/kyc-reviews
Create a KYC Review
kycReviewCreate 2 params body → 202400401404429
GET
/v1/profiles/{profileId}/kyc-reviews
Get all KYC Reviews for a profile
kycReviewList 4 params → 200401429
GET
/v1/profiles/{profileId}/kyc-reviews/{kycReviewId}deprecated
Get KYC Review by ID (V1)
kycReviewGetV1 3 params → 200401404429
PATCH
/v1/profiles/{profileId}/kyc-reviews/{kycReviewId}
Update KYC Review to get a Hosted KYC link
kycReviewRedirectUrlUpdate 3 params body → 200400401404429
GET
/v2/profiles/{profileId}/kyc-reviews/{kycReviewId}
Get KYC Review by ID
kycReviewGet 3 params → 200401404429
POST
/v2/profiles/{profileId}/kyc-requirements/{requirementKey}
Submit a KYC Requirement
kycReviewRequirementSubmit 3 params body → 202400401404429

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are kyc-review (9 properties), kyc-requirement (5 properties). Each schema is shown below with its type and property counts.

kyc-requirement
object
An object returned as part of the [KYC Review](api-reference/kyc-review/kyc-review) object, which includes information about a required evidence, its state, an…
5 properties
kyc-review
object
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 Re…
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wise-kyc-review-api-openapi.yml Raw ↑

Other APIs Wise publishes across the network.

Wise 3ds API
Wise activity API
Wise address API
Wise balance API
Wise balance-statement API
Wise bank-account-details API
Wise batch-group API
Wise bulk-settlement API
Wise card API
Wise card-kiosk-collection API
Wise card-order API
Wise card-sensitive-details API
Where this information came from

This is an independent, third-party profile of Wise kyc-review API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.