APIs and agents
REST API reference
Browse the existing authoring endpoints and download the OpenAPI specification.
PeopleTide Content · HTTP integration guides
Authoring base URL.
Use https://content.peopletide.com/api/v1 from a trusted integration with a site-specific agent bearer key. Human-only actions use the existing signed-in workspace session. OpenAPI is available publicly at /api/v1/openapi.json.
# Run from a trusted terminal. Set SITE_ID and CMS_AGENT_TOKEN first.
curl --fail-with-body \
-H "Authorization: Bearer $CMS_AGENT_TOKEN" \
"https://content.peopletide.com/api/v1/sites/$SITE_ID/content?limit=25"Existing authoring endpoints.
The endpoint index below comes from the application’s OpenAPI operation list. Request payloads follow the document, revision-write, and proposal contracts described in these guides. Site setup, grants, and token administration require human administrator access.
/api/v1/sites/api/v1/sites/api/v1/sites/{site}/schemas/api/v1/sites/{site}/schemas/{type}/api/v1/sites/{site}/content/api/v1/sites/{site}/content/{id}/api/v1/sites/{site}/content/{id}/api/v1/sites/{site}/content/{id}/history/api/v1/sites/{site}/content/{id}/references/api/v1/sites/{site}/snapshots/api/v1/sites/{site}/snapshots/{id}/api/v1/sites/{site}/snapshots/{id}/review/api/v1/sites/{site}/changesets/api/v1/sites/{site}/changesets/api/v1/sites/{site}/changesets/{id}/api/v1/sites/{site}/changesets/{id}/validate/api/v1/sites/{site}/changesets/{id}/approve/api/v1/sites/{site}/changesets/{id}/reject/api/v1/sites/{site}/releases/api/v1/sites/{site}/releases/{id}/rollback/api/v1/sites/{site}/tokens/api/v1/sites/{site}/tokens/api/v1/sites/{site}/tokens/{id}/api/v1/sites/{site}/grants/api/v1/sites/{site}/grants/{id}/api/v1/sites/{site}/media/api/v1/sites/{site}/media/api/v1/sites/{site}/media/{id}/finalize/api/v1/sites/{site}/changes/api/v1/sites/{site}/review-tasksPublic delivery endpoints.
GET /delivery/v1/{org}/{site}/current.json discovers the release; GET the returned manifest and object URLs. GET and HEAD serve published artifacts, and OPTIONS supports browser delivery. These endpoints use neither the authoring bearer key nor workspace cookies.
Errors are JSON.
Error responses contain error and optional details. Read details for validation or conflict context. Common statuses are 400 invalid input, 401 authentication required, 403 access or human approval required, 404 missing resource, and 409 revision or release conflict. Bound retries for transient failures; do not automatically resubmit approval actions.