Validate Requirements
POST/api/v2/listings/validate-requirements
Dry-run a set of products against a template on a sales-channel instance and report, per product, required and recommended field coverage (present vs missing) plus any validation issues. Nothing is created or published.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body
- product_ids (integer[], required) — the products to validate.
- sales_channel_id (integer, required) — the sales-channel instance to validate against.
- sales_channel_product_template_id (integer, required) — the template to apply; must belong to the given sales channel.
Each product's status is one of ready, needs_attention (a required field is missing a value), or error (a field has an invalid value).
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.