Skip to main content
PATCH
Renames, archives, or sets a flag’s value — the change your servers pick up on their next poll.

Authorization

string
required
Bearer token for authentication. Format: Bearer <your-api-key>

Required Permission

FLAGS_WRITE

Path Parameters

string
required
The flag’s UUID.

Body Parameters

Every field is optional — send only what you are changing.
string
New name, 1–100 characters.
string | null
New description, up to 500 characters. Send null to clear it.
string
The kind of value the flag holds. Must be sent together with value.
JsonValue
The new value. Must be sent together with type.
string
shared or server. Unlike the key, the runtime is mutable — a flag made client-readable by mistake can be closed without recreating it under a new key.
boolean
true removes the flag from the published payload, so servers stop seeing it. false restores it. The flag itself is kept either way, so its key cannot be silently reused.
The key cannot be changed. Servers reference a flag by key, so renaming one would silently orphan every server reading it. Delete the flag and create a new one if you need a different key.
Changing the value means restating the type. The pair is what servers parse, and validating them together is what keeps a number flag from ending up holding a string. Sending one without the other fails with 400.

Response

Returns the updated flag — the same shape as a single entry in GET /flags.

Status Codes

Locked flags

A flag beyond your allowance rejects edits to its name, description, value and runtime with 403. Archiving and deleting stay allowed — they are how you get back under the allowance. See Feature Flags.