---
title: "Changes to Update feature"
method: PUT
path: "/features/{id}"
---

# Changes to Update feature

`PUT /features/{id}`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 9 of 139 revisions.

- **2026-09-03** `e36fe54e0efb`: 2 info
- **2026-07-15** `f8ecf435d25d`: 3 warning
- **2026-07-09** `7d57386313c7`: 10 breaking, 9 warning, 16 info
- **2026-07-09** `4b1a811c4179`: 22 breaking, 16 warning, 9 info
- **2026-06-29** `7857ddc6e44d`: 1 warning
- **2026-05-18** `8ec2edea6b20`: 6 warning
- **2026-04-06** `95af41a12111`: 6 warning, 12 info
- **2026-03-20** `d563556cdaf1`: 5 info
- **2026-03-02** `8ab89ff34fdc`: 1 info

## Changes

- **2026-09-03** `e36fe54e0efb`: 2 info
  - added the new optional request property `alert_settings/alert_threshold_type`
  - added the optional property `alert_settings/alert_threshold_type` to the response with the `200` status
- **2026-07-15** `f8ecf435d25d`: 3 warning
  - added the new `not_implemented` enum value to the `code` response property for the response status `400`
  - added the new `not_implemented` enum value to the `code` response property for the response status `404`
  - added the new `not_implemented` enum value to the `code` response property for the response status `500`
- **2026-07-09** `7d57386313c7`: 10 breaking, 9 warning, 16 info
  - the `filters/items/` request property type changed from no type to `object`
  - the `metadata` request property type changed from no type to `object`
  - the `reporting_unit` request property type changed from no type to `object`
  - the `metadata` response's property type changed from no type to `object` for status `200`
  - the `meter/aggregation` response's property type changed from no type to `object` for status `200`
  - the `meter/filters/items/` response's property type changed from no type to `object` for status `200`
  - the `meter/reset_usage` response's property type changed from no type to `string` for status `200`
  - the `reporting_unit` response's property type changed from no type to `object` for status `200`
  - the `status` response's property type changed from no type to `string` for status `200`
  - the `type` response's property type changed from no type to `string` for status `200`
  - added the new `BILLING_PERIOD` enum value to the `meter/reset_usage` response property for the response status `200`
  - added the new `NEVER` enum value to the `meter/reset_usage` response property for the response status `200`
  - added the new `archived` enum value to the `status` response property for the response status `200`
  - added the new `boolean` enum value to the `type` response property for the response status `200`
  - added the new `config` enum value to the `type` response property for the response status `200`
  - added the new `deleted` enum value to the `status` response property for the response status `200`
  - added the new `metered` enum value to the `type` response property for the response status `200`
  - added the new `published` enum value to the `status` response property for the response status `200`
  - added the new `static` enum value to the `type` response property for the response status `200`
  - added the new optional request property `filters/items/key`
  - added the new optional request property `filters/items/values`
  - added the new optional request property `reporting_unit/conversion_rate`
  - added the new optional request property `reporting_unit/unit_plural`
  - added the new optional request property `reporting_unit/unit_singular`
  - added the optional property `meter/aggregation/bucket_size` to the response with the `200` status
  - added the optional property `meter/aggregation/expression` to the response with the `200` status
  - added the optional property `meter/aggregation/field` to the response with the `200` status
  - added the optional property `meter/aggregation/group_by` to the response with the `200` status
  - added the optional property `meter/aggregation/multiplier` to the response with the `200` status
  - added the optional property `meter/aggregation/type` to the response with the `200` status
  - added the optional property `meter/filters/items/key` to the response with the `200` status
  - added the optional property `meter/filters/items/values` to the response with the `200` status
  - added the optional property `reporting_unit/conversion_rate` to the response with the `200` status
  - added the optional property `reporting_unit/unit_plural` to the response with the `200` status
  - added the optional property `reporting_unit/unit_singular` to the response with the `200` status
- **2026-07-09** `4b1a811c4179`: 22 breaking, 16 warning, 9 info
  - the `alert_settings/critical/threshold` request property type changed from `number` to `string`
  - the `alert_settings/info/threshold` request property type changed from `number` to `string`
  - the `alert_settings/warning/threshold` request property type changed from `number` to `string`
  - the `filters/items/` request property type changed from `object` to no type
  - the `metadata` request property type changed from `object` to no type
  - the `reporting_unit` request property type changed from `object` to no type
  - the `alert_settings/critical/threshold` response's property type changed from `number` to `string` for status `200`
  - the `alert_settings/info/threshold` response's property type changed from `number` to `string` for status `200`
  - the `alert_settings/warning/threshold` response's property type changed from `number` to `string` for status `200`
  - the `created_at` response's property format changed from `date-time` to no format for status `200`
  - the `group/created_at` response's property format changed from `date-time` to no format for status `200`
  - the `group/updated_at` response's property format changed from `date-time` to no format for status `200`
  - the `metadata` response's property type changed from `object` to no type for status `200`
  - the `meter/aggregation` response's property type changed from `object` to no type for status `200`
  - the `meter/created_at` response's property format changed from `date-time` to no format for status `200`
  - the `meter/filters/items/` response's property type changed from `object` to no type for status `200`
  - the `meter/reset_usage` response's property type changed from `string` to no type for status `200`
  - the `meter/updated_at` response's property format changed from `date-time` to no format for status `200`
  - the `reporting_unit` response's property type changed from `object` to no type for status `200`
  - the `status` response's property type changed from `string` to no type for status `200`
  - the `type` response's property type changed from `string` to no type for status `200`
  - the `updated_at` response's property format changed from `date-time` to no format for status `200`
  - removed the request property `filters/items/key`
  - removed the request property `filters/items/values`
  - removed the request property `reporting_unit/conversion_rate`
  - removed the request property `reporting_unit/unit_plural`
  - removed the request property `reporting_unit/unit_singular`
  - removed the optional property `meter/aggregation/bucket_size` from the response with the `200` status
  - removed the optional property `meter/aggregation/expression` from the response with the `200` status
  - removed the optional property `meter/aggregation/field` from the response with the `200` status
  - removed the optional property `meter/aggregation/group_by` from the response with the `200` status
  - removed the optional property `meter/aggregation/multiplier` from the response with the `200` status
  - removed the optional property `meter/aggregation/type` from the response with the `200` status
  - removed the optional property `meter/filters/items/key` from the response with the `200` status
  - removed the optional property `meter/filters/items/values` from the response with the `200` status
  - removed the optional property `reporting_unit/conversion_rate` from the response with the `200` status
  - removed the optional property `reporting_unit/unit_plural` from the response with the `200` status
  - removed the optional property `reporting_unit/unit_singular` from the response with the `200` status
  - removed the `BILLING_PERIOD` enum value from the `meter/reset_usage` response property for the response status `200`
  - removed the `NEVER` enum value from the `meter/reset_usage` response property for the response status `200`
  - …7 more
- **2026-06-29** `7857ddc6e44d`: 1 warning
  - added the new `config` enum value to the `type` response property for the response status `200`
- **2026-05-18** `8ec2edea6b20`: 6 warning
  - removed the optional property `details` from the response with the `400` status
  - removed the optional property `details` from the response with the `404` status
  - removed the optional property `details` from the response with the `500` status
  - added the new `too_many_requests` enum value to the `code` response property for the response status `400`
  - added the new `too_many_requests` enum value to the `code` response property for the response status `404`
  - added the new `too_many_requests` enum value to the `code` response property for the response status `500`
- **2026-04-06** `95af41a12111`: 6 warning, 12 info
  - removed the optional property `error` from the response with the `400` status
  - removed the optional property `error` from the response with the `404` status
  - removed the optional property `error` from the response with the `500` status
  - removed the optional property `success` from the response with the `400` status
  - removed the optional property `success` from the response with the `404` status
  - removed the optional property `success` from the response with the `500` status
  - added the optional property `code` to the response with the `400` status
  - added the optional property `code` to the response with the `404` status
  - added the optional property `code` to the response with the `500` status
  - added the optional property `details` to the response with the `400` status
  - added the optional property `details` to the response with the `404` status
  - added the optional property `details` to the response with the `500` status
  - added the optional property `http_status_code` to the response with the `400` status
  - added the optional property `http_status_code` to the response with the `404` status
  - added the optional property `http_status_code` to the response with the `500` status
  - added the optional property `message` to the response with the `400` status
  - added the optional property `message` to the response with the `404` status
  - added the optional property `message` to the response with the `500` status
- **2026-03-20** `d563556cdaf1`: 5 info
  - added the new optional request property `group_id`
  - added the new optional request property `reporting_unit`
  - added the optional property `group` to the response with the `200` status
  - added the optional property `group_id` to the response with the `200` status
  - added the optional property `reporting_unit` to the response with the `200` status
- **2026-03-02** `8ab89ff34fdc`: 1 info
  - added the optional property `meter/aggregation/expression` to the response with the `200` status

---

[Operation](https://skmtc.dev/flexprice/apis/flexprice-api/docs/features/:id/put.md) - [API](https://skmtc.dev/flexprice/apis/flexprice-api.md) - [Page](https://skmtc.dev/flexprice/apis/flexprice-api/changes/features/:id/put)
