---
title: "upsertCarriers - Upsert carriers"
method: POST
path: "/v1/orders/channels/{channel_id}/carriers"
tags: ["Carriers"]
---

# upsertCarriers - Upsert carriers

`POST /v1/orders/channels/{channel_id}/carriers`

<div class="extension-title">Description</div>

Use this API to share the channel's allowed list of carriers with Mirakl Connect, and keep it synchronized over time.

**Important:**
- You must provide the complete list of carriers in a single request, any carriers not included will be deleted
- If the marketplace allows it, you can add an "Other" carrier to cover unlisted carriers; otherwise, only include formally supported carriers
- We recommend sharing the full list of carriers: Mirakl Connect automatically maps carriers with slight naming differences


<div class="api-description-extension">
<div class="extension-title">Call Frequency</div>

<div class="recommended-call-frequency">Recommended usage: When the channel's allowed list of carriers changes</div>
<div class="max-call-frequency">Maximum usage: 1 / hour</div>
</div>

## Path parameters

- `channel_id` string, required

## Request body

- UpsertCarriersRequest
  - `carriers` CarrierRequest[], required — List of carriers available on the channel
    - `channel_carrier_id` string, required — Unique identifier of the carrier on the channel
    - `name` string, required — Display name of the carrier

## Response `204`

No Content

## Other responses

- `400` — Bad Request
- `404` — The channel was not found. This may occur if: - The channel_id does not exist - The channel does not belong to the calling connector's technology

---

[API](https://skmtc.net/mirakl/apis/mirakl-connect-channel-platform-apis.md) · [All operations](https://skmtc.net/mirakl/apis/mirakl-connect-channel-platform-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mirakl/mirakl-connect-channel-platform-apis/revisions/7810ddb35640/schema)