Authorizations
Use the /v1/oauth2/token endpoint to obtain an access token and pass it as a Bearer token in the Authorization header.
Path Parameters
The unique identifier code of the feature. This is the code that was specified when the feature was created.
Response
Successfully retrieved the feature with all its properties and privileges
Complete feature object returned by the API, including all properties and server-generated fields like timestamps Core properties that define a feature - a capability or functionality that can be entitled to customers through plans or subscriptions
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. Date and time in ISO 8601 format.
"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