Skip to main content

Update feature type lifetime

PUT 

<your-unleash-url>/api/admin/feature-types/:id/lifetime

Updates the lifetime configuration for the specified feature flag type. The expected lifetime is an integer representing the number of days before Unleash marks a feature flag of that type as potentially stale. If set to null or 0, then feature flags of that particular type will never be marked as potentially stale.

When a feature flag type's expected lifetime is changed, this will also cause any feature flags of this type to be reevaluated for potential staleness.

Request

Path Parameters

    id stringrequired

Bodyrequired

updateFeatureTypeLifetimeSchema

    lifetimeDaysintegernullablerequired

    The new lifetime (in days) that you want to assign to the feature flag type. If the value is null or 0, then the feature flags of that type will never be marked as potentially stale. Otherwise, they will be considered potentially stale after the number of days indicated by this property.

    Possible values: <= 2147483647

    Example: 7

Responses

featureTypeSchema

Schema
    idstringrequired

    The identifier of this feature flag type.

    Example: kill-switch
    namestringrequired

    The display name of this feature flag type.

    Example: Kill switch
    descriptionstringrequired

    A description of what this feature flag type is intended to be used for.

    Example: Kill switch feature flags are used to quickly turn on or off critical functionality in your system.
    lifetimeDaysintegernullablerequired

    How many days it takes before a feature flag of this typed is flagged as potentially stale by Unleash. If this value is null, Unleash will never mark it as potentially stale.

    Example: 40

Authorization: Authorization

name: Authorizationtype: apiKeyin: headerdescription: API key needed to access this API

Request Collapse all
Base URL
<your-unleash-url>
Auth
Parameters
— pathrequired
Body required
{
  "lifetimeDays": 7
}
ResponseClear

Click the Send API Request button above and see the response here!