Listings

Update marketplace options

Merges the listing's marketplace-specific options.

PATCH
/v1/listings/{listingId}/marketplace-options

This is the door for marketplaceOptions after creation: the Listing PATCH returns 400 if it receives that field. Send a map by namespace, with at least one namespace.

The merge is key by key inside the namespace: updating one key preserves the others in that namespace. The response is the whole map. It never calls the marketplace; the Listing becomes dirty and emits listing.updated.

Only the namespace of the Connection's marketplace is valid. A namespace from another marketplace, a URL, or a credential key returns 400 VALIDATION_ERROR with details.field equal to marketplaceOptions.

For an exception in a single publication, use oneTimeMarketplaceOptions in publish.

Authorization

api_key
headerAuthorizationBearer <token>

API key (mk_...)

Path Parameters

listingId*string
Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid

Request Body

application/json
  1. body

Options to merge, under the connected marketplace namespace. Each key replaces the same key of the stored options; other keys stay. This operation never publishes.

[key: string]?

Response Body

Every option after the merge. The listing becomes dirty; nothing is published.

application/json
  1. response

Namespaced persistent options validated against the connected marketplace capability.

[key: string]?
curl -X PATCH "https://example.com/v1/listings/497f6eca-6276-4993-bfeb-53cbbbba6f08/marketplace-options" \  -H "Content-Type: application/json" \  -d '{    "mercadolivre": {      "saleTerms": [        {          "id": "WARRANTY_TYPE",          "value": "123"        }      ]    }  }'
{  "mercadolivre": {    "saleTerms": [      {        "id": "WARRANTY_TYPE",        "value": "123"      }    ]  }}