Partially update a tier or its levels.
display_name, lifecycle settings, and levels. Only the fields you include in the request body are changed; omitted fields are left as-is.
When updating levels, existing levels are matched by key and updated in place. New keys create new levels (a rank is required for new levels). Changes to qualification thresholds take effect for future evaluations but do not retroactively re-evaluate participants who have already qualified.
The tier key is immutable and cannot be changed after creation.
API key passed in the X-API-Key header.
Fields to update
Human-readable name shown in dashboards and reports
255Levels to upsert. Existing levels (matched by key) are updated; new keys create new levels.
Lifecycle configuration updates (retention mode, qualification period, downgrade policy, counter rollover)
Updated tier
A tier definition with its levels, lifecycle configuration, and metadata
When this tier was created (RFC 3339)
"2024-01-15T10:30:00Z"
Human-readable name
"Loyalty Status"
Unique identifier for this tier
"550e8400-e29b-41d4-a716-446655440000"
Tier key used in API calls and rule actions
"status"
Ordered list of levels within this tier
Lifecycle configuration (retention mode, qualification period, downgrade policy, counter rollover)
Program this tier belongs to
"550e8400-e29b-41d4-a716-446655440001"
When this tier was last modified (RFC 3339)
"2024-01-15T10:30:00Z"