Skip to main content

20 docs tagged with "v3"

View all tags

Audiobook Tracks

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

Bulk Operations

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 (publication page or reader).

Bulk Operations

Create multiple orders in a single API call. The bulk endpoint processes orders concurrently, making it significantly faster than sequential individual requests.

Content API v1 → v3 Migration Guide

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).

Content Sharing

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.

Create Content

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

Delete Content

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

Get Content

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

Get Order

Retrieve a specific order by its UUID or external ID.

List Content

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

List Orders

Retrieve a paginated list of orders with powerful filtering, sorting, and response shaping capabilities.

Orders API v1 → v3 Migration Guide

This document provides a comprehensive migration guide from Orders API v1 to v3, including breaking changes, schema differences, and practical migration steps.

Permission Orders

Grant content access without creating payment records. Use when you process payments externally and only need Publica.la for content delivery.

Report Orders

Assign content access and create payment records in Publica.la's financial system. Required for marketplace content sales or when you need financial tracking for externally processed payments.

Sale Orders

Initiate Publica.la's checkout flow where customers pay directly through the platform. Orders start with pending status and transition to approved after successful payment via integrated payment gateways (Stripe, MercadoPago, etc.).

Supported Content Languages

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.

Update Content

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

X

Graph View