Skip to main content

Request

Headers

Device context headers

Targeting rules match against these optional headers. Send them to get rule-resolved values; omit them all and every flag falls back to its environment default.

Rate limit headers

Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset from the flags bucket. 429 responses include Retry-After.

Query parameters

Response

Values are typed according to each flag’s value type (boolean, integer, double, string, or JSON), and keys are sorted alphabetically.

How a value is resolved

For each flag, in order:
  1. An active per-device override matching X-Device-ID wins outright.
  2. Otherwise targeting rules are evaluated in priority order; the first rule whose conditions all match and whose rollout admits the device supplies the value. Rules are skipped entirely when no device context headers are sent.
  3. Otherwise the flag’s value for that environment is used — its “on” value when the flag is active in that environment, its “off” value when it is not.
Flags with no configured value in the requested environment are omitted from the map. A request carrying identity headers sees that app’s flags plus the organization-wide ones; an API-key request without identity headers sees only the organization-wide flags. Every returned flag is recorded as an evaluation, which is what the dashboard’s flag evaluation feed reports.

List environments

Same authentication and rate-limit bucket. Returns your organization’s flag environments in sort order.

Tier limits

See also