Frequently Asked Questions

This documentation covers common questions and details for the Product Type Definitions API. For questions or concerns not covered by this documentation, contact Selling Partner API support or post your question on our Community page.

How fresh are Amazon Product Type Definitions?

Unless specifying a previous productTypeVersion, the Amazon product type definitions always describe the latest up-to-date Amazon catalog requirements.

Are all Amazon Product Types Available with the Product Type Definitions API?

No.

Amazon is continually expanding support for new and existing Amazon product types in the Product Type Definitions API. For the up-to-date list of available Amazon product types, use the Product Type Definitions API.

What version of JSON Schema is Used?

Amazon product type definition JSON Schemas extend JSON Schema 2019-09. Refer to the accompanying Amazon Product Type Definition Meta-Schema (v1) documentation for more details.

How will future versions of JSON Schema be leveraged?

As future versions of JSON Schema are adopted by the Product Type Definitions API, they will be accompanied by a new version release of the Product Type Definitions API and Amazon Product Type Definition Meta-Schema.

Future versions of JSON Schema will not be adopted by existing versions of the Product Type Definitions API or Amazon Product Type Definition Meta-Schema.

Do Product Type Definition JSON Schemas include custom vocabulary?

Most Amazon catalog requirements are described utilizing standard JSON Schema 2019-09 vocabulary. However, there are a few requirements that necessitate extending JSON Schema with custom vocabulary. Refer to the accompanying Amazon Product Type Definition Meta-Schema (v1) documentation for more details.

Am I required to implement validation for custom vocabulary?

No.

The Amazon Product Type Definition Meta-Schema (v1) uses custom vocabulary to fully describe Amazon catalog requirements. Validating data with custom data enables you to prevent most listings-related issues from occurring before submitting to Amazon. However, it is up to you to implement such validation. Without implementing this validation, submitting data to Amazon can produce listings-related issues after submission to Amazon.

Do I need custom code to use JSON Schemas?

Yes.

The amount of custom code depends upon your application. Example scenarios:

• Using an open source library with validation of custom vocabulary: Leveraging an open source library to handle most JSON Schema validation means custom code is necessary to retrieve schemas from the Product Type Definitions API, to implement validation of custom vocabulary, and to integrate with the open source library.

• Using an open source library without validation of custom vocabulary: Leveraging an open source library to handle most JSON Schema validation means custom code is necessary to retrieve schemas from the Product Type Definitions API and to integrate with the open source library.

What open source libraries are available?

Dozens of open source libraries and implementations are available to validate data, render user interfaces, and generate code. Refer to JSON Schema Tooling for a full list.

Amazon does not directly support or endorse any specific open source or commercial libraries and implementations. Examples provided in this documentation are for reference only.

What examples are available for validating data with Product Type Schemas?

The accompanying Amazon Product Type Definition Meta-Schema (v1) documentation includes example integrations with open source libraries to validate data with custom vocabulary in .NET (C#), Java, and JavaScript (Node.js).

How do I report issues with Amazon Product Type Definitions?

For issues specific to the Product Type Definitions API or the content of Amazon product type definition JSON Schemas, contact Selling Partner API support.