Generate All Documents
POST /global-context/generate-all
Generate the whole Global Context set, in dependency order.
ONE-SHOT. The app refuses this with a 409 once a pipeline has completed for
the organisation - it is the onboarding path, not a rebuild. To rebuild
documents that already exist use POST /global-context/regenerate.
Requires intelligence data for website_url to exist already; without it
the documents would be generated from nothing.
Authorizations
Parameters
Header Parameters
Request Body required
Mirrors campaign_builder.routers.global_context.GenerateAllDocumentsRequest.
ONE-SHOT. The app refuses this with a 409 once a pipeline has completed for
the org, which is why POST /global-context/regenerate exists - use that
to rebuild documents that already exist.
object
The company website every document is generated against. Intelligence data must already exist for it.
Responses
202
Successful Response
object
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.
object
422
Validation Error