---
title: "Upload client data"
method: PUT
path: "/v1/verifications/{verificationId}/data"
tags: ["Document Authentication"]
---

# Upload client data

`PUT /v1/verifications/{verificationId}/data`

Use this endpoint to upload the client’s personal data. <br /><br /><img src="https://files.readme.io/310d4d3-Inline_Caution.svg" align="left" alt="Important" /> **Important:** Before using this endpoint, see the <a href="https://docs.fourthline.com/docs/docauth-integration-api">integration guide</a>. <br /><br /><img src="https://files.readme.io/310d4d3-Inline_Caution.svg" align="left" alt="Caution" /> **Caution:** If you make another request with the same `verificationId`, it overwrites the existing case.

## Path parameters

- `verificationId` string, required

## Headers

- `Content-Type` string
- `Authorization` string, required — The `access_token` returned in your most recent [Create access token](https://docs.fourthline.com/reference/create-access-token) response.

## Request body

- object
  - `person` object — The client’s <Glossary>personal data</Glossary>. <br /><br />Requirements: For API integration object is required.
    - `type` string, required — The type of entity the client is. <br />Enum: <br />• `Legal Entity`: The client is a company or organization with legal rights and obligations. <br />• `Legal Person`: The client is a non-human entity with legal rights and obligations. <br />• `Natural Person`: The client is a living human.
    - `name` string — The client’s full name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: John James Smith <br /><img src="https://files.readme.io/5c5228a-Inline_Configurable.svg" align="left"/> **Configurable**: You can configure this parameter to be required or optional on request
    - `initials` string — The client’s initials. <br /><br />Format: Alphabetical characters <br /><br />Example: JCCF
    - `firstName` string, required — The client’s first name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: John
    - `middleName` string — The client’s middle name(s). <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: James
    - `lastName` string, required — The client’s last name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Smith
    - `otherLastName` string — Any other last name the client uses, e.g. married name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes
    - `nationality` string, required — The client’s nationality. <br /><br />Format: ISO 3166-1 alpha-3 country code <br /><br />Example: BEL
    - `gender` 'Female' | 'Male' | 'Other' | 'Unknown', required — The client’s sex <br /><br />Format: Case sensitive <br />Enum: <br />• `Female`: Female in line with ID document <br />• `Male`: Male in line with ID document <br />• `Other`: ID document contains a value other than `Male` or `Female` <br />• `Unknown`: ID document contains **no** gender field
    - `birthDate` string, required — The client’s date of birth. <br /><br />Format: Date YYYY-MM-DD <br /><br />Example: `1960-10-18`= October 18, 1960
    - `placeOfBirth` string — The city where the client was born. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Sint-Agatha-Berchem <br /><img src="https://files.readme.io/5c5228a-Inline_Configurable.svg" align="left"/> **Configurable**: You can configure this parameter to be required or optional on request
    - `countryOfBirth` string — The country where the client was born. <br /><br />Format: ISO 3166-1 alpha-3 <br /><br />Example: BEL
  - `address` object — The client’s address details. <br /><br />Requirements: For API integration that upload `person` and `emailAndPhone` data.
    - `street` string, required — The street of the client’s address. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Rue Jean-Baptiste Jansen
    - `streetNumberPrefix` string — The prefix of the street number <br /><br />Example: A1
    - `streetNumber` integer, required — The street number of the client’s address. <br /><br />Format: int32 greater than or equal to zero
    - `streetNumberSuffix` string — The suffix of the street number. <br /><br />Format: Alphabetical characters, spaces, hyphens, and numerals <br /><br />Example: 123A
    - `postalCode` string, required — The zip code of the client’s address. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: 1082 <br /><br /><img src="https://files.readme.io/ad2486a-Inline_Note.svg" align="left"/>**Note**: We use Google’s Address Validation API and depend on the quality of their data
    - `region` string — The region of the client’s address <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Brussels Capital Region
    - `city` string, required — The city of the client’s address. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: `London`
    - `country` string, required — The country of the client’s address. <br /><br />Format: ISO 3166-1 alpha-3 <br /><br />Example: BEL
  - `emailAndPhone` object — The client’s email address and phone number(s). <br /><br />Requirements: For API integration object is required.
    - `email` string, required — The client’s email address. <br /><br />Format: Maximum 254 characters [_-a-zA-Z0-9.+]+@a-zA-Z0-9 <br /><br />Example: `j.smith@example.com`
    - `phone` string — The client’s landline number. <br /><br />Format: Must include the country code and begin with `00` or `+` **without** spaces <br /><br />Example: 003281123456 **or** +3281123456
    - `mobile` string, required — The client’s mobile phone number. <br /><br />Format: Must include the country code and begin with `00` or `+` **without** spaces <br /><br />Example: `00324123456789` **or** `+324123456789`
  - `previousDocumentData` object — The client’s previous ID document data. <br />If the client was onboarded by: <br />• Fourthline: **do not** include this object. <br />• Another KYC provider: This object is **required**.
    - `BirthDate` string, required — The client’s date of birth. <br /><br />Format: Date YYYY-MM-DD <br /><br />Example: `1960-10-18`= October 18, 1960
    - `FirstName` string, required — The client’s first name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: John
    - `LastName` string, required — The client’s last name. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Smith
    - `Nationality` string, required — The client’s nationality. <br /><br />Format: ISO 3166-1 alpha-3 country code <br /><br />Example: BEL
    - `PlaceOfBirth` string, required — The city where the client was born. <br /><br />Format: Alphabetical characters, spaces, hyphens, and apostrophes <br /><br />Example: Sint-Agatha-Berchem

## Response `200`

The client data was uploaded successfully

- object — A successful response is empty.

## Other responses

- `400` — Invalid request parameters
- `422` — The request could not be processed

---

[API](https://skmtc.net/fourthline/apis/fourthline-apis.md) · [All operations](https://skmtc.net/fourthline/apis/fourthline-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fourthline/fourthline-apis/versions/7991ae7c8383/schema)