Skip to content

Native feature flags ​

Feature flags turn a capability of an app on or off without publishing a new version. Each flag is a boolean and is isolated by company, DSL application and environment (development, staging or production). Only DSL applications owned by the active company are valid.

Administration requires a user session with the OWNER or ADMIN role. The backend re-checks the current membership on every request and derives the company from the authenticated context. A companyId sent by the client is not accepted.

Get the evaluation identifier ​

Each app + environment pair has a stable public identifier. An OWNER or ADMIN obtains or creates it with:

http
POST /feature-flags/clients
Authorization: Bearer <token>
Content-Type: application/json

{
  "applicationId": "<tenant-dsl-app-uuid>",
  "environment": "development"
}

The 200 response contains publicClientId, applicationId and environment. The ID can be included in the client app configuration to evaluate that scope's flags. It is not a secret and grants no administrative access.

Manage flags ​

http
POST /feature-flags
Authorization: Bearer <token>
Content-Type: application/json

{
  "applicationId": "<tenant-dsl-app-uuid>",
  "environment": "development",
  "key": "new_dashboard",
  "name": "New dashboard",
  "enabled": false
}

Creation responds 201 and returns the flag id.

  • key is unique within the company, app and environment; it accepts letters, digits, dot, dash and underscore, and must start with a letter.
  • If enabled is omitted it is stored as false.
  • GET /feature-flags?applicationId=<uuid>&environment=development lists the scope.
  • GET /feature-flags/:id reads one flag; PATCH /feature-flags/:id changes key, name or enabled; DELETE /feature-flags/:id removes it and responds 204.
  • A flag from another company is never revealed and answers 404.

Public evaluation ​

http
GET /feature-flags/public/<publicClientId>/evaluate

The route requires no session and accepts no companyId, applicationId or environment. The server resolves the scope from the stored identifier and returns only the configured keys and their boolean values:

json
{
  "flags": {
    "new_dashboard": false
  }
}

Keys that do not exist are absent; the consumer can apply its own default. The browser SDK integrates evaluation with OpenFeature and must fall back to those defaults when the service is unavailable.

Security and scope limits ​

A flag controls interface presentation or behaviour. It does not replace authorization, permissions, roles or backend entitlements: every protected operation must revalidate those rules on the server. The first version has no per-user targeting, segments, percentage rollout, variants or experiments.