---
title: "Changes to Replace mutable segment fields"
method: PUT
path: "/api/v1/user/segments/{id}"
---

# Changes to Replace mutable segment fields

`PUT /api/v1/user/segments/{id}`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 1 of 4 revisions.

- **2026-07-26** `996f96a11758`: 2 breaking, 1 warning, 40 info

## Changes

- **2026-07-26** `996f96a11758`: 2 breaking, 1 warning, 40 info
  - added the new required `header` request parameter `X-CSRF-Token`
  - added required request body
  - for the `path` request parameter `id`, the min was set to `1.00`
  - api operation id `putUserSegmentsById` was added
  - added the media type `application/json` for the response with the status `200`
  - added the media type `application/json` for the response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - added the non-success response with the status `422`
  - added the optional property `_alias_of` to the response with the `404` status
  - added the optional property `action` to the response with the `404` status
  - added the optional property `allowed` to the response with the `404` status
  - added the optional property `allowed_parameters` to the response with the `404` status
  - added the optional property `code` to the response with the `404` status
  - added the optional property `daily_limit` to the response with the `404` status
  - added the optional property `date` to the response with the `404` status
  - added the optional property `detail` to the response with the `404` status
  - added the optional property `fields` to the response with the `404` status
  - added the optional property `key` to the response with the `404` status
  - added the optional property `limit` to the response with the `404` status
  - added the optional property `limited_by` to the response with the `404` status
  - added the optional property `login_url` to the response with the `404` status
  - added the optional property `max_bytes` to the response with the `404` status
  - added the optional property `maximum` to the response with the `404` status
  - added the optional property `needed` to the response with the `404` status
  - added the optional property `ok` to the response with the `404` status
  - added the optional property `parameter` to the response with the `404` status
  - added the optional property `plan` to the response with the `404` status
  - added the optional property `projection` to the response with the `404` status
  - added the optional property `reason` to the response with the `404` status
  - added the optional property `remaining` to the response with the `404` status
  - added the optional property `reset_at` to the response with the `404` status
  - added the optional property `reset_at_human` to the response with the `404` status
  - added the optional property `retry_after` to the response with the `404` status
  - added the optional property `retry_after_s` to the response with the `404` status
  - added the optional property `shortfall` to the response with the `404` status
  - added the optional property `slug` to the response with the `404` status
  - added the optional property `source_catalog_version` to the response with the `404` status
  - added the optional property `status` to the response with the `404` status
  - added the optional property `upgrade` to the response with the `404` status
  - …3 more

---

[Operation](https://skmtc.dev/openmercantil/apis/openmercantil-public-api/docs/api/v1/user/segments/:id/put.md) - [API](https://skmtc.dev/openmercantil/apis/openmercantil-public-api.md) - [Page](https://skmtc.dev/openmercantil/apis/openmercantil-public-api/changes/api/v1/user/segments/:id/put)