Organization Settings

Update Compliance Settings

Patch certification status, keyed by certification id.

PARTIAL: only the ids you send are touched. An id the product does not support is IGNORED rather than rejected - that is the app's behaviour, so read the response back rather than assuming the write landed.

put/org/settings/compliance

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/org/settings/compliance
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

certificationsobject required

Certification id -> status. Unknown ids are ignored by the server.

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.