content:write
The content:write scope allows you to create content from completed IdeaClouds, re-trigger generation on existing IdeaCloud-linked content, and report where your integration has externally published content.
Endpoints
Report external publication
CallPOST /v1/public/content/{id}/posted after your integration publishes the page. This requires X-API-Key, content:write, and the API Access (API_ACCESS) plan entitlement.
Use the Hrizn content UUID returned by create, not an external CMS, job, or IdeaCloud ID. Send only { "posted_url": "https://www.example.com/blog/hybrid-suv-guide" }. The URL is trimmed, must be absolute HTTP(S), must contain no credentials, and must be at most 4096 characters after trimming. Unknown body fields are rejected; site, customer, and actor IDs are never accepted. The key-associated site constrains both reads and conditional writes; missing and other-site content return the same 404 not_found.
A successful 200 response contains data with id, posted_url, marked_posted_at, and publish_state: "published". The server records the first report time; retries and URL corrections preserve it. A retry with the current URL is a no-op. A different URL replaces it, and the last successfully applied update wins. Serialize corrections and stop superseded retries; no event version or X-Idempotency-Key response caching is supported. Authorization reruns on each call. Retry only the latest intended payload after a contention 409 conflict.
The callback reuses the manual posted marker. It does not crawl, independently verify, or publish the page, and leaves generation, CMS publishing state, and telemetry unchanged. It does not add content to /content/published or unlock /content/{id}/publish-data. Backfill known content-ID/URL pairs with one request per pair; no scanning, batch, unpublish, or new MCP tools are provided.
See Mark content as externally posted for an example and error handling, including validation (400), scope or plan denial (403), not found (404), contention (409), rate limiting (429), service unavailability (503), and unexpected failures (500).
Create content
selected_question_ids to choose which questions to cover; otherwise the IdeaCloud’s recommended questions are used.
Request body
For
qa and expert, include selected_staff in the create request or save it
first with PATCH /ideaclouds/{id}/settings. The base
PATCH /ideaclouds/{id} path is not an endpoint.
Example
Response — 202 Accepted
Status codes
Create content in batch
Request body
Each item accepts the same fields as the single Create content endpoint.
Example
Response — 202 Accepted
Response — Partial failure
Status codes
Regenerate content
Path parameters
Request body
Example
Response — 202 Accepted
Status codes
Error response — Missing scope
If your API key does not includecontent:write, any request to these endpoints returns:
