Upsert sales channel mapping
This endpoint allows the marketplace to map its trade policies with a seller's affiliate. A seller can have multiple trade policies associated with the same marketplace, creating different affiliates. The mapping allows the seller to segment catalog, pricing, inventory, logistics, and payments in the marketplace.
Permissions
Any user or API key must have at least one of the appropriate License Manager capabilities in order to successfully execute this request. Otherwise, they will receive a 403 status code error. These are the applicable capabilities for this endpoint:
| Product | Category | Resource |
|---|---|---|
| Seller Register | Seller Administration | Save seller |
You can create a custom role with this resource or use one of the following predefined roles:
| Role | Resource |
|---|---|
| Seller Manager | Save Seller |
❗ Assigning a predefined role to users or application keys typically grants permission to several License Manager resources. If some of these permissions are not required, consider creating a custom role. For more information about security, see Best practices for using application keys.
Path parameters
Name of the VTEX account that belongs to the marketplace. The notification will be posted into this account.
Environment to use. Used as part of the URL.
A string that identifies the seller in the marketplace. This ID must be created by the marketplace and informed to the seller before the integration is built.
Query parameters
Marketplace's account name, the same one inputted on the endpoint's path.
Headers
Type of the content being sent.
HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
Request body
Example request
[
{
"marketplaceSalesChannel": 1,
"sellerChannel": "GCB"
},
{
"marketplaceSalesChannel": 2,
"sellerChannel": "DFT"
}
]Response
OK