v1

latestOpenAPI 3.0.02026-07-141,4077,1665.2 MB

Feature Flags

Add a variant to a feature flag

Adds a single new variant to an existing feature flag. This endpoint is additive-only: it never modifies existing variants. A request whose key already exists on the flag is rejected with 409 Conflict; a value whose type does not match the flag's value_type is rejected with 400. The server generates the variant UUID and returns it in the response body; callers (for example, the flag-migration tool) need this UUID to reference the new variant in subsequent allocation syncs.

post/api/v2/feature-flags/{feature_flag_id}/variants

Path parameters

feature_flag_idstring uuid required

Example:550e8400-e29b-41d4-a716-446655440000

The ID of the feature flag.

Request body

keystring required

The unique key of the variant.

namestring required

The name of the variant.

valuestring required

The value of the variant as a string.

Example request

{
  "key": "variant-abc123",
  "name": "Variant ABC123",
  "value": "true"
}

Response

Created

created_atstring date-time

The timestamp when the variant was created.

idstring uuid required

The unique identifier of the variant.

keystring required

The unique key of the variant.

namestring required

The name of the variant.

updated_atstring date-time

The timestamp when the variant was last updated.

valuestring required

The value of the variant as a string.

Example response

{
  "created_at": "2023-01-01T00:00:00Z",
  "id": "550e8400-e29b-41d4-a716-446655440002",
  "key": "variant-abc123",
  "name": "Variant ABC123",
  "updated_at": "2023-01-01T00:00:00Z",
  "value": "true"
}