KOkobaltlabs
marketing-guidelines

Set Requirements State Bulk

Changed on

Turn several requirements off, remove them, or put them back, in one press.

The library is long enough that the interesting selections are not one row: a search that finds seventeen restatements of the same enforcement note is a single decision, and making it seventeen times is how it does not get made.

Removal stays archival. ARCHIVED keeps the requirement and every version of it readable, which is the point on regulated compliance material; there is no hard delete here.

One requirement's refusal never fails the batch, and every id gets an outcome — the three refusals are refuse_state_change, the same function the rollout-consistency worklist uses, so the two surfaces cannot drift about what a person may do to a requirement.

post/marketing/guidelines/requirements/state

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/marketing/guidelines/requirements/state
  • Auth
    none declared

Request body

requirement_idsstring[] required
state'active' | 'disabled' | 'archived' | 'superseded' | 'proposed' required

Whether a requirement is in the working library, and if not, why not.

All of them are recorded as revisions, so every one is reversible and readable.

ARCHIVED and SUPERSEDED are deliberately distinct: ARCHIVED is a person deciding this obligation does not apply to them, SUPERSEDED is a newer decomposition of the same guideline taking over. A regeneration must never overwrite the first with the second — that would erase a human decision.

change_notestring nullable

Response

Successful Response

appliedinteger required
skippedinteger required

Changes

  • 425d5b8a3c17Revision changes
    • warning

      added the new proposed enum value to the /// response property for the response status

    • info

      added the new proposed enum value to the request property