Content API overview

The Content API manages the content surfaces that TPC uses for retrieval, publishing, and public markdown delivery.

Surfaces

Surface	Use it for	Primary scope
Content lifecycle (`/api/v1/content`)	Create, generate, review (approve/reject/revise), publish, and manage product content.	`content:read`, `content:write`
Site pages (deprecated)	Legacy CRUD alias of the content surface; use `/api/v1/content` instead.	`content:read`, `content:write`
Content documents and review drafts	Read and update content, metadata, domains, and review workflows through `/api/v1/content`.	`content:read`, `content:write`
llms.txt	Read and manage generated llms.txt resources.	`content:read`, `content:write`
Apps and app routes	Manage app configuration and route resources.	`content:read`, `content:write`

Start with /api/v1/content for product pages, docs pages, and marketing content. Created and generated pages land in a review queue (GET /api/v1/content?productId=PRODUCT_ID&status=pending_review) and publish only after approval (POST /api/v1/content/{draftId}/review).

Common workflow

Create an API key with content:read.
List existing resources for a product.
Add content:write only when your integration needs mutations.
Send Idempotency-Key on writes so retries are safe.
Store x-request-id with your job logs.

Site pages migration

Move legacy site-page integrations to the content lifecycle API.

Content documents

Work with generated and reviewed content documents.