# Update Mappings Request

Update the mapping of the uploaded file to match that of the header within it. You can add or remove the required number of mapping points in the Request Body.

Endpoint: PUT /dataCleaning/jobs/{id}/mappings
Version: 1.10.9
Security: bearerToken

## Path parameters:

  - `id` (string, required)

## Request fields (application/json):

  - `mappings` (array, required)
    Example: [{"mapping":"name","value":"0"}]

  - `mappings.mapping` (string, required)
    Enum: "companyId", "orgNumber", "name", "tradingName", "aliasName", "previousName", "phone", "email", "address1", "address2", "address3", "town", "postcode", "region", "country", "countryCode", "vatNumber", "taxCode", "personalID", "personalLimit"

  - `mappings.value` (string, required)
    Value follows array indexing, meaning each column is identified by number, starting at 0
    Example: "0"

## Response 200 fields (application/json):

  - `mapping` (string)

  - `value` (string)

## Response 400 fields (application/json):

  - `correlationId` (string)
    A unique ID assigned to this request.

  - `message` (string)

  - `details` (string)
    Provides further information on why the request was rejected

## Response 401 fields (application/json):

  - `error` (string)

## Response 403 fields (application/json):

  - `message` (string)
    Example: "Access forbidden"

## Response 404 fields (application/json):

  - `correlationId` (string)
    A unique ID assigned to this request.

  - `message` (string)

  - `details` (string)
    Provides further information on why the request was rejected