Meet Amazon's apparel size-attribute requirements using the SP-API Product Type Definitions API
domain: developer-docs.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call the Product Type Definitions API to retrieve the JSON schema of required/conditionally-required attributes for your apparel product type
Populate Apparel Size System, Apparel Size Class, and Apparel Size, which are required for apparel product types (dresses, sweaters, blazers, coats, vests, etc.)
Set Target Gender and Age Range Description correctly, since they determine which additional attributes (e.g., Apparel Body Type, Apparel Height Type) become required
Choose the correct Size Class value (numeric, numeric_range, alpha, alpha_range, age, or age_range) matching how the item is actually sized
Submit the listing via the Listings Items API using the validated attribute set, and handle any submission errors against the product type schema
Known gotchas
These size-attribute rules are catalog-wide and apply identically whether you submit through SP-API or the Seller Central UI — you can't bypass them by going through the API
Required attributes vary by the combination of product type, Target Gender, and Age Range Description, so a schema pulled for one apparel product type won't necessarily match another
Amazon has changed apparel size-standard requirements before, so validate current field requirements per product type at submission time rather than caching an old schema
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?