Authentication
Generate an API key from Feature Flags → API Keys in the dashboard. Each key is scoped to a single project and must be passed as a bearer token on every request. For more detail on creating and rotating keys, see API Keys.Resolve all flags for a record
org-0ujsswThIGTUYm2K8FjOOfXtY1K) as the path parameter. The API key must belong to the same project that owns the record — requests referencing records from other projects return a 404.
Example request:
flags object maps each group flag key to its resolved value:
enabledis the final decision — the server applies the rollout dice-roll for you, so if the flag is on but the record falls outside the rollout,enabledisfalse.rolloutis the configured rollout percentage (0–100).sourceis"record"when the value comes from a per-record override, or"group-default"when it falls back to the group flag’s default.
?env= query parameter (the environment’s key or name) to resolve flags for a specific environment; when omitted, the project’s default environment is used. If the value doesn’t match any environment, environment is null and flags is {}.
TypeScript integration
Check a single global flag
If you need to check one global flag rather than resolving a full record, use the check endpoint documented in Global Flags. Like every project-scoped endpoint, it accepts either your API key or a dashboard session:?env= you pass):
source is "cache" when the result was served from the 60-second Redis cache, or "global" when freshly computed. As with the SDK endpoint, enabled already reflects the rollout roll.