Skip to content

Environments and API keys

A project is one of your applications. Each has a Development and a Production environment, and they share nothing: features, plans, Customers, subscriptions and overrides all belong to one environment. Test freely in Development.

Customer IDs are unique within an environment. Use your own opaque ID, matching ^[A-Za-z0-9._:-]{1,255}$, and never put names or emails in it. Seal0 stores nothing else about a Customer.

Keys are created by Members in the Console (API keys), never through the API. Each belongs to one environment.

Authorization: Bearer s0_prod_<key_id>_<secret>
  • Development keys start with s0_dev_, production keys with s0_prod_.
  • A key is shown once. Seal0 keeps only a keyed hash of the secret.
  • Unknown, malformed and revoked keys all get 401 invalid_api_key.
Scope May call Use it for
evaluate the two evaluation endpoints only application servers that check entitlements
full every endpoint setup and billing code that manages features, plans, Customers, subscriptions, overrides and usage

An evaluate key calling anything else gets 403 insufficient_scope.

API keys are secrets. Never put them in browser, mobile or desktop code. The TypeScript SDK refuses to run in a browser unless you pass dangerouslyAllowBrowser: true, for trusted internal tools only.

Each Account’s Seal0 plan includes a number of API requests per period. Every API-key request that passes authentication counts, including 4xx answers. Past the allowance and its grace margin, requests get 429 usage_limit_exceeded until the period resets. The SDKs don’t retry that. Plan and usage in the Console shows where you are.