18 docs tagged with "Content"

Manage audio tracks for audiobook content. Tracks are individual audio files (chapters, sections) that make up an audiobook.

Create multiple content items in a single API call. Files are not processed immediately, processing is triggered on-demand when a user accesses the content (product page or reader).

Share every owned content item that belongs to one or more collections with a list of target tenants in a single API call. The endpoint validates the request synchronously and queues the sharing work in the background.

Manage your store's digital catalog: list, create, update, and delete content items.

This document compares Content API v1 and v3 and provides a practical migration guide for integrators. The v3 feed is designed for speed, bandwidth efficiency, and flexibility via cursor pagination and response shaping (fields and includes).

This section covers the programmatic ways to get products into your store and keep them up to date. There are three, and they solve different problems:

Distribute content to other tenants' catalogs using the sharewithtenants_ids field. This allows a content owner to make their content available in other tenants' stores without duplicating the content item.

Add new content items to your catalog. Supports all content types: PDF, EPUB, audiobooks, physical products, and external links.

Remove content items from your catalog. This operation is permanent and irreversible.

Retrieve a specific content item by its internal ID or external ID.

Read the products a list of the target user holds. Any list of the store can be read, private ones included.

Retrieve a paginated list of your store's catalog with powerful filtering, sorting, and response shaping capabilities.

Read the reading lists of any user of your store, and manage the products they hold, from your own platform.

Add and remove products in any list of any user of your store: the favorites list, a custom list the user created, or a list the user collaborates on. What you write here is what the user sees in the storefront and in the reader.

An ONIX intake ingests your catalog from an ONIX 3.0 feed. We create an SFTP account and a private storage area for you and send you the password; you upload the feed and the content files there, and we create and update the products in your store from what the feed says. Use it when you are onboarding a large catalog, or when your metadata already flows to distributors and retailers as ONIX.

A scheduled automation publishes PDF editions from a folder in an S3 bucket on a schedule you define, with no integration to build. Use it when you release on a predictable calendar (a daily newspaper, a weekly magazine) and prefer naming files to a convention over writing code.

Content languages define the language of the content itself (e.g., the language a book is written in). This is different from the store language, which controls the storefront interface.

Modify existing content items. Update metadata, pricing, access settings, files, or any other content attributes.