Kinde · Module

Feature Flags API

Kinde’s Feature Flags API lets authenticated machine-to-machine clients create, edit, override, and delete feature flags through the Management API. API-created flags support string, integer, and boolean types; JSON flags must be created in the dashboard.

How it works

The Feature Flags API lets a machine-to-machine application use the Kinde Management API to create, update, override, and delete feature flags. Requests require a valid access token with the relevant feature-flag scope; API-created flags can be string, integer, or boolean, while JSON flags must originate in the dashboard.

Syntax

HTTP requests to the Kinde Management API using a Bearer access token

Returns

The page describes feature-flag management operations rather than one single return type; individual API responses depend on the requested operation.

Key points

The API provides programmatic lifecycle management instead of requiring every flag change to be made in the admin interface.
API clients need a machine-to-machine application configured for Management API access.
Every Management API request must be authenticated with a valid access token.
Overrides let you target a different value to a particular environment or organization.
When creating a flag, choose one of the documented API types: str, int, or bool.
JSON flags are supported in the dashboard, but they are not part of the API's creation type set.

Common mistakes

Do not try to create a JSON flag by sending type json through the API; create it in the dashboard instead.
Although dashboard-created JSON flags can later be overridden or deleted through the API, their type cannot be set by an API call.

Example: Read feature flags

const token = await getManagementApiToken();

const response = await fetch(
  "https://<your-kinde-domain>/api/v1/feature_flags",
  {
    headers: { Authorization: `Bearer ${token}` }
  }
);

if (!response.ok) throw new Error(`HTTP ${response.status}`);
const flags = await response.json();
console.log(flags);

Fetches feature flags from the Kinde Management API using a machine-to-machine access token.

When to use it

Create and update flags from deployment or operations tooling.

Automated release administration

Override a flag for a specific environment or organization.

Targeted rollout

Delete obsolete flags through an authenticated API workflow.

Flag cleanup

Interview questions

QHow do you access the Feature Flags API?

Use a machine-to-machine application to connect to the Kinde Management API, then authenticate requests with a valid access token. The API supports adding, editing, overriding, and deleting feature flags.

Follow-up: Which permissions should the application receive? Grant only the required feature-flag scopes, such as read, create, update, or delete, matching the operations it performs.

QWhich flag types can the API create?

The API accepts str for strings, int for integers, and bool for booleans. JSON is not an API-createable type, even though it is available in the Kinde dashboard.

Follow-up: How would you provision a JSON flag? Create it in the dashboard first, then use the API only for supported management operations such as overrides or deletion.

QWhat does the API allow you to override?

A flag can be overridden for an environment or organization, allowing a different value from the general flag configuration. This supports targeted releases without changing the base flag definition.

Follow-up: What should be checked before performing an override? Confirm that the flag exists, the target environment or organization is correct, and the access token includes the required update permission.

Kinde Management API
machine-to-machine application
valid access token
environment override
organization override
str
int
bool

Source: Manage feature flags through the Kinde API. Checked 2026-10-15.