Tier Structures

Update tier structure

<Info>

<Badge color="gray">Documentation in progress</Badge>

This documentation is in progress. The parameters, fields, request and response bodies, and other data may be subject to change. If you need more information or you want to share feedback, contact Voucherify support or your Technical Account Manager.

</Info>

Updates a tier structure. All properties are optional; provided values are merged with the existing tier structure. When type is provided as POINT_EARNED, point_earned is required and point_balance must be null; when type is POINT_BALANCE, point_balance is required and point_earned must be null. When the tier structure is not in DRAFT status, only name and metadata may be updated; attempting to update other properties results in a validation error.

put/v2/loyalties/tier-structures/{tierStructureId}

Path parameters

idstring required

Unique tier structure identifier.

Request body

namestring

Display name of the tier structure.

type'POINT_BALANCE' | 'POINT_EARNED'

Tier qualification tracking model. If provided, the matching tracking settings object (point_balance or point_earned) becomes required.

metadataobject nullable

Free-form key/value object holding custom attributes.

Response

The updated tier structure.

idstring required

Unique tier structure identifier.

namestring required

Display name of the tier structure.

type'POINT_BALANCE' | 'POINT_EARNED' required

Tier qualification tracking model.

metadataobject required

Free-form key/value object holding custom attributes. Defaults to {}.

status'DRAFT' | 'ACTIVE' | 'INACTIVE' | 'DELETED' required

Current lifecycle status of the tier structure.

created_atstring date-time required

Creation timestamp (ISO 8601).

updated_atstring date-time nullable required

Last update timestamp (ISO 8601), or null if never updated.

object'tier_structure' required

Object type discriminator. Always tier_structure.

Changes

Changed in 3 of the 62 revisions of this API.5410

Jul 31, 2026v2703a0a42ea43322See the full diff
- ▲
  added subschema #1 subschema #2 to the request body allOf list
  request-body-all-of-added
- ▲
  the request property const value changed from NO_EXPIRATION to NO_RETENTION
  request-property-const-changed
- ▲
  removed the enum value NO_EXPIRATION of the request property /////
  request-property-enum-value-removed
- ●
  removed subschema #1 subschema #2 from the request body allOf list
  request-body-all-of-removed
- ●
  added the new NO_RETENTION enum value to the / response property for the response status
  response-property-enum-value-added
- ○
  added the new NO_RETENTION enum value to the request property /////
  request-property-enum-value-added
- ○
  removed the NO_EXPIRATION enum value from the / response property for the response status
  response-property-enum-value-removed
This revision also has 10 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 17, 2026v24cbaee5a82d58See the full diff
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
- ○
  added the optional property to the response with the status
  response-optional-property-added
Jul 17, 2026v226ef7b3dd1ef22See the full diff
- ▲
  added subschema #1 subschema #2 to the request body allOf list
  request-body-all-of-added
- ▲
  added subschema #3 subschema #4 subschema #5 to the //// request property allOf list
  request-property-all-of-added
- ●
  removed subschema #1 subschema #2 from the request body allOf list
  request-body-all-of-removed
- ●
  removed subschema #3 subschema #4 subschema #5 from the //// request property allOf list
  request-property-all-of-removed

Full history