Configuration and evaluation
Frozen legacy delivery
GET /api/v1/config requires an environment sdk_ key and returns the full
legacy document. GET /api/v1/public-config requires a pub_ key and returns
only legacy flags with clientEnabled: true; legacy rules and overrides are
always empty on the client route.
Advanced configuration
GET /api/v1/advanced-config returns composed core schema v1. Environment
credentials infer app/environment from the key. CLI and app-admin reads supply
?appId=<id>&env=<slug>.
sdk_ key receives server delivery. A pub_ key receives only
explicit client-visible flags and dependencies, with arbitrary metadata removed
by default.
ETag revalidation and quota
Send the last opaque ETag inIf-None-Match. A matching credential,
representation, source, and version returns 304 with no body and renews the
SDK freshness window.
Both 200 and 304 environment config responses count as one monthly sync.
Free includes 25,000 syncs per month per environment; Pro includes 1,000,000.
304 contributes zero response bytes. Management reads with cli_ or admin_
credentials do not count as environment config syncs.
Quota exhaustion returns 429 with code
MONTHLY_CONFIG_SYNC_QUOTA_EXCEEDED. Metering unavailability fails closed with
retryable 503 CONFIG_SYNC_METERING_UNAVAILABLE.
Remote server evaluation
POST /api/v1/evaluate requires an environment sdk_ key. Use it when
targeting rules must remain in Superflag rather than being synchronized to the
application server.