---
title: "Merge a Package"
method: POST
path: "/v2.0/packages/{packageId}/merge"
tags: ["Packages"]
---

# Merge a Package

`POST /v2.0/packages/{packageId}/merge`

Creates a task to merge a [Package](https://docs.cognigy.com/ai/resources/build/packages).

## Path parameters

- `packageId` string, required

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Request body

- object
  - `resourceIds` string[], required
  - `strategies` object[]
    - `_id` string
    - `rename` string — explicitly sets a new name for the imported resource
    - `autoRename` boolean — If set to true, will append a "counter-suffix" to the name in case the name already exists in the agent.
    - `identityConflictStrategy` 'replace' | 're-identify' | 'abort' | 'merge' — Defines what should be done in case the agent already contains a resource with the same id.
    - `mergeStrategy` object
      - `replaceContent` boolean
      - `replaceStructure` boolean
      - `localeOverrides` object[]
        - `replaceContent` boolean
        - `localeId` string
  - `localeMapping` object[]
    - `agentLocaleId` string
    - `packageLocaleId` string

## Response `202`

Task to merge the Package successfully created.

- object
  - `_id` string
  - `status` 'queued' | 'active' | 'done' | 'cancelling' | 'cancelled' | 'error' — The status of the task
  - `type` string
  - `parameters` object
  - `lastChangedAt` number
  - `lastCreatedAt` number
  - `currentStep` integer
  - `totalStep` integer

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/revisions/85b2872bdfb7/schema)