Skip to content

Quickstart

Pack the catalog in the console, mint a member API key, call check from your backend.

You need:

  • An account and organization at e10s.io
  • A service account with a member API key

API host: https://api.e10s.io. Keys and roles: Authentication. Console: Console.

1. Pack the catalog in the console

At e10s.io, in this organization:

  1. Create features sso (flag) and seats (limit).
  2. Create a catalog plan pro that grants SSO and seats 10.
  3. Create subscriber cust_123 (your customer id).
  4. Subscribe them to pro.

2. Mint a key

Service accounts → create a service account (for example production). New service accounts get the runtime role, which can only check entitlements. On that service account, Create key. The key carries the service account's role.

Copy the plaintext once.

3. Check access from your backend

Flag

POST /org/subscribers/cust_123/entitlements/check
X-API-Key: e10s-k-2-…
Content-Type: application/json

{ "feature": "sso" }

{
  "feature": "sso",
  "kind": "flag",
  "allowed": true,
  "source": "plan"
}

Limit

{ "feature": "seats" }

{
  "feature": "seats",
  "kind": "limit",
  "limit": 10,
  "source": "plan"
}

4. Gate in your product

See Check access for a backend snippet (check a flag, compare a limit to your usage).

Catalog via the API

To create features and subscribers from a script, use a key on a developer service account. A runtime key gets 403 on those routes.

Next