# Uploads an attachment to be linked to a brand. The attachment will be automatically assigned to the new Brand Orders when needed.

Upload an attachment to be linked to a brand.

Endpoint: POST /v1/projects/{projectId}/us/brands/{brandId}/attachments
Version: 1.0.0
Security: OAuth2

## Path parameters:

  - `projectId` (string, required)
    Customer's project id

  - `brandId` (string, required)
    Customer's brand id

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

  - `file` (string, required)
    File content body

  - `attachmentType` (string, required)
    Attachment type
    Enum: "COMPANY_BANNER", "COMPANY_LOGO"

## Response 201 fields (application/json):

  - `attachmentId` (string)
    Unique identifier of the attachment.

  - `fileName` (string)
    Human readable name of the attachment.

  - `attachmentType` (string)
    Attachment type
    Enum: same as `attachmentType` (2 values)

  - `mimeType` (string)
    MIME type of the attachment file.

  - `uploadStatus` (string)
    Status of the file uploaded
    Enum: "COMPLETED", "WAITING", "FAILED"

  - `createTime` (string)
    Create time of the request. ISO date time format in UTC.

  - `updateTime` (string)
    Update time of the request. ISO date time format in UTC.

## Response 401 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type. This URI reference should provide a human-readable explanation of the problem type when dereferenced.

  - `title` (string, required)
    A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for localization purposes.

  - `body` (object) — one of:
    - variant 1:
      - `errors` (array)
        Detailed information about the error. This field can contain multiple error details to provide more context about the error that occurred.
      - `errors.pointer` (string)
        JSON pointer to the field that caused the error, following RFC 6901.
      - `errors.detail` (string)
        A human-readable explanation specific to this occurrence of the problem. Like title, this field is not intended for end users, but rather for developers to understand the details of the error that occurred.
    - variant 2:
      - `detail` (string)
        A human-readable explanation of the error that occurred.