Create a new feature for a Full Stack project

post

https://api.convert.com/api/v2/accounts/{account_id}/projects/{project_id}/features/add

Defines a new feature within a Full Stack project. Requires a name, a unique key, and a list of variables associated with the feature. Each variable has a key, type (string, boolean, integer, float, json), and a default value. Features are used in Full Stack experiments to control different code paths or configurations.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

account_id

integer

required

ID of the account that owns the retrieved/saved data

project_id

integer

required

ID of the project into which the feature is to be stored

Body Params

Represents a feature flag or a set of configurable variables within a Full Stack project. Features are used in 'a/b_fullstack' or 'feature_rollout' experiences to control application behavior or content dynamically, often from the server-side or within client-side applications using an SDK. Each feature has a unique key for programmatic access and a list of variables whose values can be altered per experience variation. Knowledge Base: "Full Stack Experiments on Convert".

name

string

required

length ≤ 100

A user-defined, friendly name for the feature (e.g., "New Checkout Process", "Beta User Dashboard"). This name appears in the Convert UI.

status

string

enum

Defaults to active

The current status of a feature:

active: The feature is active and can be used in Full Stack experiments. Its variables can be controlled by experiences.
archived: The feature is archived and no longer available for new experiments. Existing experiments using it might behave based on last known configuration or default values.

Allowed:

key

string

length ≤ 32

A unique, machine-readable string key for this feature (e.g., "new_checkout_flow", "beta_dashboard_enabled"). This key is used by the SDKs to identify and retrieve the feature's configuration and variable values. It's typically auto-generated from the name if not specified, but can be user-defined.

description

string

length ≤ 200

An optional, more detailed explanation of the feature's purpose, what it controls, or its intended use cases.

variables

array of objects

required

An array of FeatureVariable objects that define the configurable parameters associated with this feature. For example, a feature "Button Customization" might have variables like "buttonColor" (string), "buttonText" (string), and "isEnabled" (boolean). The values of these variables can be different for each variation of an experience that uses this feature.

variables*

Responses

201Detailed information for a single feature in a Full Stack project, including its name, key, status, description, and an array of its variables (each with a key, type, and default value).

defaultIndicates an error occurred while processing the request. The code provides an HTTP status code, message offers a human-readable explanation or an array of validation errors, and fields (if present) specifies which input fields were problematic.