Construct a valid ONIX 3.0 book metadata record for retailer/distributor feeds
domain: editeur.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Download the current ONIX 3.0/3.1 Specification, XML schemas, and Implementation and Best Practice Guide from editeur.org/93/release-3.0-downloads.
Model the record around required composites: Product Identifier (ISBN-13), Descriptive Detail (title, contributors, subject codes), Publishing Detail, and Product Supply (price, availability).
Follow the Implementation and Best Practice Guide's codelists for controlled-vocabulary values (e.g., product form, contributor role) rather than inventing custom values.
Validate the finished XML against EDItEUR's published XSD schema before submitting it to a retailer or distributor.
Note the industry deadline: Amazon requires senders to transition fully from ONIX 2.1 to ONIX 3 for eBooks by March 2026.
Known gotchas
ONIX 3.0 and 3.1 are not fully backward compatible -- 3.1 removed data elements deprecated in 3.0, so pick a version deliberately per trading-partner requirements.
ONIX is a metadata message format, not a live API -- there is no ONIX endpoint; it is typically delivered as a file to each trading partner.
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?