# BATCH creation of brands

This endpoint allows you to create multiple brands at once. Batch
creation is processed asynchronously in same way as for example products
snapshot, but it does not have resultUrl in response. Instead, you can check
attribute log which contains successfully created brands and errors.



See how Asynchronous requests work on
our developer's portal.



File with data for update must be in JSONL (jsonlines) format. Each line must contain one
brand in JSON format. Maximum size of file is 100MB.



Structure of JSON row is same as structure of JSON for single brand
creation above. See Brand batch create schema for more details.



Asynchronous job process jsonl file row by row and try to validate and
save data. If there is any error, row is skipped and error is logged,
but it does not stop processing of other rows. In Log, every product is
identified by its position in file (starting from 1).

Endpoint: POST /api/brands/batch
Version: 1.0.0
Security: shoptetAccessToken, shoptetPrivateApiToken

## Header parameters:

  - `Content-Type` (string, required)

## Request fields (application/json):

  - `batchFileUrlPath` (string, required)
    Url to batch file with products data. File must be in JSONL format.

## Response 202 fields (application/json):

  - `data` (object, required)

  - `data.jobId` (string, required)
    token of job

  - `errors` (array,null, required)

  - `errors.errorCode` (string, required)
    Short text error identification

  - `errors.message` (string, required)
    Descriptive error message

  - `errors.instance` (string, required)
    Identification of the entity referenced

  - `metadata` (object, required)

  - `metadata.requestId` (string, required)
    Request identifier. Useful for logging/reporting purposes.

## Response 409 fields (application/json):

  - `data` (object,null)

  - `errors` (array,null)

  - `metadata` (object)


## Response 404 fields