# Create a content transfer operation

Creates a new operation to transfer one or more specified items from your *source* environment. You must specify a unique ID of your choice for the transfer, which you'll use later in the transfer workflow.
Make this request in your *source* environment.
If you reuse a previous transfer ID, the transfer operation associated with that ID will be overwritten (if it was not previously deleted using this API).
By default, a transfer will only include single items based on the paths you specify, and it will replace any duplicate items found in the destination environment. You can override these settings to include descendants or choose a different merge strategy as needed.

Endpoint: POST /sitecore/api/content/transfer/v1/transfers
Version: v1.0
Security: bearerAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer JWT

## Request body:

  - `application/json, text/json, application/xml, text/xml, application/x-www-form-urlencoded, text/html` (unknown)
    The request body containing your transfer configuration and a unique transfer ID.

## Request fields (application/json):

  - `Configuration` (object)

  - `Configuration.DataTrees` (array)
    One or more objects representing the content items you want to transfer. Each object represents an item at a specific path, determines whether to include descendants, and specifies how to handle conflicts with existing files.

  - `Configuration.DataTrees.ItemPath` (string)
    The path of the content item you want to transfer.
    Example: /sitecore/content/Home/MyItem

  - `Configuration.DataTrees.Scope` (string)
    Whether the specified item should be transferred on its own or include all descendants.
    Enum: "SingleItem", "ItemAndDescendants"

  - `Configuration.DataTrees.MergeStrategy` (string)
    The method you want to use to handle conflicts with items that already exist in the destination. `OverrideExistingTree` removes the item and all its descendants from the destination before writing the transferred items. This is the only strategy that can delete existing items.
    Enum: "OverrideExistingItem", "KeepExistingItem", "OverrideExistingTree"

  - `Configuration.Database` (string)
    The name of the database associated with the source.
    Example: master

  - `TransferId` (string)
    A universally unique identifier (UUID) representing the transfer. This is a value of your choice.
Format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx` and containing only hexadecimal characters (`0`-`9`, `a`-`f`).
    Example: 00000000-0000-0000-0000-000000000000

## Response 202:

  - `202` (unknown)
    Content transfer creation was initiated successfully.

## Response 400:

  - `400` (unknown)
    Invalid request data or validation failed.

## Response 400 fields (application/json):

  - `Error` (string)

## Response 401:

  - `401` (unknown)
    Unauthorized.

## Response 401 fields (application/json):

  - `Error` (string)

## Response 403:

  - `403` (unknown)
    Forbidden.

## Response 403 fields (application/json):

  - `Error` (string)