Aggregates API v3 Overview
Programmatically provision and manage sub-tenants (aggregates) under your aggregator store. Each aggregate is a fully independent store with its own domain, catalog, and configuration.
Step-by-step guides and implementation tutorials
View all tagsProgrammatically provision and manage sub-tenants (aggregates) under your aggregator store. Each aggregate is a fully independent store with its own domain, catalog, and configuration.
Publica.la integrates AI capabilities into the reader experience through a suite of tools that help readers comprehend, interact with, and get more value from digital content. This page documents what AI features exist, how data flows through them, what providers are involved, and what controls publishers have.
Overview
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).
Manage your store's digital catalog: list, create, update, and delete content items.
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.
Provision a new sub-tenant (aggregate) under your aggregator store. The new tenant is created with its own domain, admin user, and store configuration.
Add new content items to your catalog. Supports all content types: PDF, EPUB, audiobooks, physical products, and external links.
Retrieve the details of a specific sub-tenant (aggregate) by its ID.
Retrieve a specific content item by its internal ID or external ID.
Retrieve a specific order by its UUID or external ID.
Retrieve a paginated list of all sub-tenants (aggregates) under your aggregator store.
Retrieve a paginated list of your store's catalog with powerful filtering, sorting, and response shaping capabilities.
Retrieve a paginated list of orders with powerful filtering, sorting, and response shaping capabilities.
This document provides a comprehensive migration guide from Orders API v1 to v3, including breaking changes, schema differences, and practical migration steps.
Manage customer purchases and content access on your Publica.la platform.
Modify the configuration of an existing sub-tenant (aggregate). All fields are optional; only include fields you want to change.