# Upserts Third Party Locations (TPLocations) in bulk

This endpoint allows for bulk upserting of TPLocations.
            
### Creating a TPLocations
The fields that are required to create a TPLocation are type and code
            
### Updating a TPLocations
include the query parameter, upsert=true
            
When a validation error occurs, the entire request will fail.

Endpoint: POST /third-party/{syncId}/locations
Version: v3.0: 3.26.2.2
Security: Auth API User Token

## Path parameters:

  - `syncId` (string, required)

## Query parameters:

  - `upsert` (boolean)

## Request fields (application/json-patch+json):

  - `type` (string,null)

  - `code` (string,null)

  - `description` (string,null)

  - `parentCode` (string,null)
    Third Party's code for parent location of this location

  - `alternateCode` (string,null)

  - `storeId` (string,null)
    YD Store ID

  - `storeCode` (string,null)
    YD Store Code for use with Import TP Locations

## Response 201 fields (text/plain):

  - `id` (integer)

  - `code` (string,null)

  - `type` (string,null)

  - `description` (string,null)

  - `createdAt` (string)

  - `updatedAt` (string)

  - `store` (object)

  - `syncConfig` (object)

## Response 400 fields (text/plain):

  - `message` (string,null)

  - `code` (string,null)

  - `path` (array,null)

  - `locations` (array,null)

  - `locations.line` (integer)

  - `locations.column` (integer)

  - `exception` (string,null)

  - `extensions` (object,null)

## Response 500 fields (text/plain):

  - `message` (string,null)

  - `errors` (array,null)

  - `errors.extensions` (string,null)


## Response 429 fields