SnozeDevelopers
API referenceAdmin

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.

PATCH
/v1/admin/flags/{flagId}

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

flagId*string

Request Body

application/json
  1. body
enabled?boolean|null
rollout?number|null
status?|null
reason?string|null

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X PATCH 'https://api.snoze.dev/v1/admin/flags/string' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "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"  }}

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.