Creates a new feature that represents a capability or functionality that can be entitled to customers. Features are the building blocks of your entitlement system - they define what can be granted to customers and what aspects can be configured. Each feature can have multiple privileges that allow fine-grained control over its behavior (e.g., a ‘seats’ feature might have ‘max’ and ‘max_admins’ privileges). Once created, features can be assigned to plans with specific privilege values.
Use the /v1/oauth2/token endpoint to obtain an access token and pass it as a Bearer token in the Authorization header.
Request payload for creating a new feature. Features represent entitleable capabilities that can be assigned to customers through plans.
Unique identifier for the feature across your entire system. This code is used when creating entitlements and should represent the feature's function (e.g., 'seats', 'api-access', 'API_STORAGE'). Allows alphanumeric characters, underscores, and hyphens.
255"USER-SEATS"
Customer-facing name of the feature that clearly describes what functionality or capability it provides. This name appears in billing interfaces and customer portals.
255"Number of seats"
Detailed explanation of what this feature provides, its limitations, and how it affects the customer's experience.
600"Number of users allowed in the account"
List of configurable privileges that define what aspects of this feature can be customized when creating entitlements. Each privilege can have different values assigned in different plans or subscriptions. Can be empty if the feature is simply on/off.
Feature was successfully created and is now available for use in plan entitlements
Complete feature object returned by the API, including all properties and server-generated fields like timestamps
Unique identifier for the feature across your entire system. This code is used when creating entitlements and should represent the feature's function (e.g., 'seats', 'api-access', 'API_STORAGE'). Allows alphanumeric characters, underscores, and hyphens.
255"USER-SEATS"
Timestamp indicating when this feature was first created in the system. Used for audit and tracking purposes.
"2023-10-01T12:00:00Z"
Customer-facing name of the feature that clearly describes what functionality or capability it provides. This name appears in billing interfaces and customer portals.
255"Number of seats"
Detailed explanation of what this feature provides, its limitations, and how it affects the customer's experience.
600"Number of users allowed in the account"
Privileges associated with this feature. Can be empty