Update a feature flag's rollout
Changes a registered flag's enablement, percentage, or segment targeting and records an audit event. Platform admins only; the payload must carry a rollout `reason`, and a `flagId` that is not registered is reported as not found.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
curl -X PATCH "https://example.com/v1/admin/flags/string" \ -H "Content-Type: application/json" \ -d '{}'{ "data": { "id": "string", "key": "string", "name": "string", "description": "string", "owner": "string", "category": "string", "controlType": "release", "registered": true, "status": "enabled", "rollout": 0, "environment": "development", "target": "string", "changedBy": "string", "changedAt": "string", "risk": "low", "linkedExperimentId": "string" }}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}Reject feature flag creation over HTTP
Always answers 405 after the admin check: feature flags are registered in product code, not created through the API. It exists so the console can explain that rule rather than return a bare 404. Platform admins only.
List the platform experiments
Returns every experiment with its variants and current status. Platform admins only.