GTM Context

Regenerate One Document

Rewrite ONE document with AI, from the current intelligence data.

Different from POST /global-context/regenerate, which rebuilds a SET against a website: this takes a single document id and rewrites it in place. The old content is replaced.

Declared LAST on this router. {doc_id} occupies the same segment as every literal above it, so registered earlier it would swallow /pipelines, /scaffold and the rest.

post/global-context/{doc_id}/regenerate

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/global-context/{doc_id}/regenerate
  • Auth: HTTP bearer

Path parameters

doc_idstring required

Document id.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataStudioPayload required

An open envelope for one settings block, document or brand artefact.

OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as "the product does not have that setting".

The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.

Changes

No recorded changes to this operation across all 2 revisions of this API.