Paligo REST API

Reference for integrating with the Paligo CCMS REST API (v2). Paligo stores structured documentation as reusable components (topics) in a DocBook 5.x–based XML format. The API covers content (documents, folders, forks), assets (images), discovery (search), ingestion (imports), publishing (productions, publish settings, outputs), localization (translation export/import), metadata (taxonomies, variables), and administration (groups, users, assignments). The flagship workflow is the content round trip: enumerate content, pull topic XML, edit it, validate, and push it back.

For any endpoint, object shape, query parameter, or enum, references/endpoints.md is the complete catalog of every resource the API exposes — start there when the task isn't a content edit (e.g. publishing, translations, users, taxonomies, variables, images).

Base URL and Authentication

https://{instance}.paligoapp.com/api/v2

{instance} is the customer's Paligo instance name. Authentication is HTTP Basic: username:apikey Base64-encoded. The API key is generated per-user in Paligo (user settings → API). The user account must have admin privileges.

curl -u "user@example.com:API_KEY" "https://example.paligoapp.com/api/v2/documents/123"

All requests/responses are JSON. Timestamps are Unix epoch integers.