Flags docs
API reference

Flags API.

The management API the console and the MCP server use, and the public config delivery route. Every endpoint, request and response, generated from the live OpenAPI spec.

Base URL

https://api.flags.productcraft.co

Auth

Authorization: Bearer …

Spec version

OpenAPI 3.0.0 · v0.1.0

Delivery

The public config download SDKs poll: `GET /v1/configs/{sdk_key}/config.json` with ETag/304, compressed bodies and CORS for browsers. Authenticated by the SDK key alone; not part of the management client.


Evaluate

Test evaluations: evaluate a sample user against a published config with the same engine the SDKs run, and see the value, the reason and the rule or percentage option that decided. Nothing is stored and the user is never logged.


History

The change history of a project: every write with who made it, its note, the config revisions it published, a diff and a human summary. Restore a version, export the history as CSV or JSON. Confidential lists show as counts, never values.


Imports

Move in from ConfigCat in one step: a dry run reports what maps, what does not and what changes form; the real run creates a project with the same environments, configs, flags, segments and targeting, and keeps every user in the same percentage bucket.


Limits

The preview limits of Flags and how much of them the workspace uses.


Revisions

Published config revisions per environment: every write that changes what SDKs download publishes a new revision of the config JSON. List them and read any kept revision byte for byte as SDKs get it.


Stale-Flags

Find dead flags: flags unchanged for a while, serving one value to everyone in every environment, or marked released or deprecated, with the literal to replace them with in code; and the weekly digest email to flag owners.


Stats

Workspace counts for dashboards: projects, configs, flags and settings, segments, recent changes, and history usage per project against the retention caps.