Contexts and Attributes

Model who is asking for flags, keep identifiers stable, and add attributes only when they help a rollout decision.

Context is the actor requesting flags

A context tells Zenmanage who or what is asking for a flag. That actor might be a user, organization, service, job runner, or another domain-specific type in your system. The stable identifier is what powers both targeting and percentage rollouts.

Context JSON structure json


{
  "type": "organization",
  "identifier": "org_acme",
  "name": "Acme Corporation",
  "attributes": [
    { "key": "region", "values": [{ "value": "us-east" }] },
    { "key": "plan", "values": [{ "value": "enterprise" }] }
  ]
}

Required fields

type: the actor category such as user, organization, or service.
identifier: the stable unique identifier used for matching and bucketing.
name: optional display text for human readability.

Attributes

Attributes are key-value lists used by attribute selectors. The current SDK data model treats every attribute as a key with one or more string values, so convert booleans, numbers, and enums into strings before you send them.

Examples include country, subscription plan, account tier, device type, or job role. Avoid sending attributes that you do not actively target.

Context header usage http


GET /v1/flags HTTP/1.1
Host: api.zenmanage.com
X-API-KEY: tok_your_environment_key_here
X-ZENMANAGE-CONTEXT: {"type":"user","identifier":"usr_123","attributes":[{"key":"country","values":[{"value":"US"}]}]}

Context vs segment

A context is the single actor being evaluated right now. A segment is a reusable grouping mechanism that rules can compare against across many evaluations.

Next step

Take the next integration step in your own stack.

Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.

View quickstarts Start free trial