Listing requirements

Tells you what to fill in to publish. Send categoryId, productType or both. With none, the answer is 400. catalogProductId narrows the result with what that catalog product already defines.

curl "$BACKEND_URL/v1/connections/$CONNECTION_ID/listing-requirements?categoryId=mock-cellphones" \
  -H "Authorization: Bearer mk_your_api_key"

Each item of fields is a field to fill in:

Example. GTIN is required, unless the seller states why there is none (EMPTY_GTIN_REASON):

{
  "path": "attributes[GTIN]",
  "scope": "marketplace_product_variant",
  "requirement": "required",
  "conditions": [
    {
      "path": "attributes[EMPTY_GTIN_REASON]",
      "operator": "absent",
      "values": []
    }
  ]
}

Read it like this: GTIN is required while attributes[EMPTY_GTIN_REASON] is missing (absent). Once the reason is filled in, the condition stops holding and GTIN is no longer required. present and absent take no values.

Each field also has the allowed values, the units (UCUM) and variationAxis, which marks a field that becomes a variation, such as color. Outside the fields, limits has the category caps, like maxPictures. To check a listing against this list, use Validate listing.

Part of Publish listings. Synchronous read, no Job, as in List categories.