Authorization: Bearer header.
Authentication
All evaluation endpoints require an SDK key issued for the target environment. Send it in theAuthorization header:
401 Unauthorized.
Some endpoints also accept
sdkKey in the request body for backward compatibility with older clients. When both are present, the Authorization header takes precedence. New integrations should rely on the header only.Endpoints
Evaluate a single flag
Resolves one flag for a given context.200 OK:
Evaluate multiple flags (batch)
Evaluate up to 100 flags in a single request. Results are returned in the same order as theevaluations array.
200 OK:
{ "enabled": false, "reason": "flag_disabled" } while the rest evaluate normally.
Maximum 100 evaluations per request. The
evaluations array must contain at least one item.Fetch flag configurations
Fetches full flag configurations (rules, rollout, enabled state) for caching. This is what the official SDKs call internally duringinitialize() and on each poll cycle.
keys[] is omitted, all active flags for the environment are returned.
Response 200 OK:
ETag header. Send it back with If-None-Match on subsequent polls to avoid re-downloading unchanged configs:
304 Not Modified with no body. Always store and send the returned ETag.

