SnozeDevelopers
API referenceAdmin

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.

POST
/v1/admin/flags

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.

Response Body

Request error — bad input, auth, scope, or state. The error code identifies which; see https://developers.snoze.dev/docs/api/errors.

application/json
  1. response
_tag*string

Specific failure name, e.g. ApiNotFound.

error*string

Stable machine-readable code, e.g. not_found. Write code against this.

message*string

Human-readable explanation. Never parse it.

status*integer

HTTP status code.

Example Request
curl -X POST 'https://api.snoze.dev/v1/admin/flags'
Example Response
{  "_tag": "ApiNotFound",  "error": "not_found",  "message": "That item does not exist, or this key cannot see it.",  "status": 404}

List the registered feature flags

Returns every feature flag registered in product code together with its current rollout state and segment targeting. Platform admins only.

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.