Management API
Flag configuration
Read and publish a flag’s targeting in one environment, toggle it, list versions and restore one.
Publishing writes the flag’s on/off state, overrides, rules and default variations for one environment and publishes a new snapshot. The write carries the version it expects; a stale one answers 409. Environments that require confirmation need confirm: true.
Restoring an earlier version creates a new version, so history is kept.
Operations
| Operation | Request | Who may call it |
|---|---|---|
| getFlagConfig | GET /api/orgs/{org}/projects/{project}/environments/{env}/flags/{flag} | viewer or above |
| publishFlagConfig | PUT /api/orgs/{org}/projects/{project}/environments/{env}/flags/{flag} | developer or above |
| toggleFlag | POST /api/orgs/{org}/projects/{project}/environments/{env}/flags/{flag}/toggle | developer or above |
| listFlagVersions | GET /api/orgs/{org}/projects/{project}/environments/{env}/flags/{flag}/versions | viewer or above |
| restoreFlagVersion | POST /api/orgs/{org}/projects/{project}/environments/{env}/flags/{flag}/restore | developer or above |
Management API requests carry a user token and are checked against the caller’s organization role. Delivery API requests carry an SDK key; the two never cross. Errors are always { error: { code, message } }.