# Submit a KYC Requirement

{% admonition type="warning" %}
This functionality is in a closed BETA.
{% /admonition %}

Submit a KYC requirement for a KYC Review.

- A KYC requirement can only be submitted if the KYC Review status is WAITING_CUSTOMER_INPUT.
- A KYC requirement should only be submitted if its state is NOT_PROVIDED and apiCollectionSupported is true.

See the KYC requirement types guide for the full list of supported requirement types, submission data structures, and accepted values.

Endpoint: POST /v2/profiles/{profileId}/kyc-requirements/{requirementKey}
Security: UserToken

## Path parameters:

  - `profileId` (integer, required)
    The profile ID.

  - `requirementKey` (string, required)
    The KYC requirement type to submit.

See the KYC requirement types guide for details on each type.
    Enum: "ACCOUNT_INTENT", "ACCOUNT_PURPOSE", "BUSINESS_ANNUAL_INCOME", "BUSINESS_AUTHORISATION_ID", "BUSINESS_AUTHORISATION_LETTER", "BUSINESS_DIRECTORS_CHECK", "BUSINESS_MONTHLY_VOLUME", "BUSINESS_REGISTRATION_DOCS", "BUSINESS_SHAREHOLDERS_CHECK", "BUSINESS_SOURCE_OF_WEALTH", "BUSINESS_SOURCE_OF_WEALTH_INFO", "BUSINESS_SOURCE_OF_WEALTH_PROOF", "BUSINESS_ULTIMATE_BENEFICIAL_OWNER_ID", "BUSINESS_USE_CASE", "ID_DOCUMENT", "PROOF_OF_TRADING_ADDRESS", "SOURCE_OF_WEALTH", "TAX_RESIDENCY", "USE_CASE_COUNTRIES"

## Request fields (multipart/form-data):

  - `submissionData` (string, required)
    A JSON string containing the following fields:

- data — an object whose fields vary by requirement type. Some requirement types do not require a data field.
- version — the submission version, currently "V1".
- kycReviewId — the ID of the KYC Review this submission belongs to.

For example, the JSON payload would look like below, but it should be included as a string value in the multipart form field:

json
{
  "data": {
    "accountPurpose": "SENDING_MONEY_TO_FRIENDS_OR_FAMILY"
  },
  "version": "V1",
  "kycReviewId": "93a903ea-636c-4c86-a25c-cf6d2bd00e81"
}


See the [KYC requirement types](/guides/product/kyc/wise-kyc/kyc-requirement-types) guide for the data structure and accepted values for each requirement type.

  - `files` (array)
    One or more files to upload. Required for certain requirement types.

See the [KYC requirement types](/guides/product/kyc/wise-kyc/kyc-requirement-types) guide for which types require files.

## Response 400 fields (application/json):

  - `type` (string)
    Example: "/errors/types/validation"

  - `title` (string)
    Example: "Validation Error"

  - `status` (integer)
    Example: 400

  - `instance` (string)

  - `detail` (string)

  - `errors` (array)

  - `errors.code` (string)

  - `errors.ref` (string)

  - `errors.detail` (string)

  - `errors.attributes` (object)


## Response 202 fields

## Response 401 fields

## Response 404 fields