# Update a invoice marketing info record

Endpoint: PATCH /invoice-marketing-info/{invoiceMarketingInfoId}
Version: 1.44
Security: bearerAuth

## Path parameters:

  - `invoiceMarketingInfoId` (integer, required)
    Invoice marketing info record identifier
    Example: 1

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

  - `file1` (multipartFile)
    Slot 1 file content (jpeg,png,gif,bmp,tiff,rtf)

  - `file2` (multipartFile)
    Slot 2 file content (jpeg,png,gif,bmp,tiff,rtf)

  - `file3` (multipartFile)
    Slot 3 file content (jpeg,png,gif,bmp,tiff,rtf)

  - `file4` (multipartFile)
    Slot 4 file content (jpeg,png,gif,bmp,tiff,rtf)

  - `patch` (array)
    JSON Patch is a format for describing changes to a JSON document as specified in RFC 6902. Refer to [jsonpatch.com](http://jsonpatch.com/) for more information

  - `patch.op` (string, required)
    The JSON Patch operation to be performed
    Enum: "add", "remove", "replace", "move", "copy", "test"

  - `patch.path` (string, required)
    A JSON-Pointer

  - `patch.value` (object)
    The value to be used within the operations

  - `patch.from` (string)
    A string containing a JSON Pointer value

## Response 200 fields (application/json):

  - `id` (integer)
    Invoice Marketing Info record identifier
    Example: 1

  - `contractOwnerSubBrandId` (integer, required)
    Contract Owner Sub-Brand Identifier

  - `invoiceTemplateId` (integer, required)
    Invoice Template Identifier

  - `createdDate` (string)
    Date when this record was created

  - `updatedDate` (string)
    Date when this record was last updated

  - `slot1` (object)

  - `slot1.type` (string, required)
    Content type for a slot
    Enum: "TEXT", "IMAGE", "RTF"

  - `slot1.textContent` (string)
    Text content

  - `slot2` (object)

  - `slot3` (object)

  - `slot4` (object)


## Response 400 fields

## Response 401 fields

## Response 403 fields

## Response 404 fields