---
title: "Changes to PATCH /api/v1/orgs/{org_uuid}/visibility/settings"
method: PATCH
path: "/api/v1/orgs/{org_uuid}/visibility/settings"
---

# Changes to PATCH /api/v1/orgs/{org_uuid}/visibility/settings

`PATCH /api/v1/orgs/{org_uuid}/visibility/settings`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 2 of 7 revisions.

- **2026-08-25** `55772030ddd3` — 15 breaking, 15 warning
- **2026-08-19** `b38f8e603649` — 5 breaking, 20 info

## Changes

- **2026-08-25** `55772030ddd3` — 15 breaking, 15 warning
  - the response property `detail` became nullable for the status `400`
  - the response property `detail` became nullable for the status `401`
  - the response property `detail` became nullable for the status `403`
  - the response property `detail` became nullable for the status `404`
  - the response property `detail` became nullable for the status `409`
  - the response property `detail` became optional for the status `400`
  - the response property `detail` became optional for the status `401`
  - the response property `detail` became optional for the status `403`
  - the response property `detail` became optional for the status `404`
  - the response property `detail` became optional for the status `409`
  - the `detail` response's property type/format changed from `string`/`` to ``/`` for status `400`
  - the `detail` response's property type/format changed from `string`/`` to ``/`` for status `401`
  - the `detail` response's property type/format changed from `string`/`` to ``/`` for status `403`
  - the `detail` response's property type/format changed from `string`/`` to ``/`` for status `404`
  - the `detail` response's property type/format changed from `string`/`` to ``/`` for status `409`
  - removed the optional property `code` from the response with the `400` status
  - removed the optional property `code` from the response with the `401` status
  - removed the optional property `code` from the response with the `403` status
  - removed the optional property `code` from the response with the `404` status
  - removed the optional property `code` from the response with the `409` status
  - removed the optional property `fields` from the response with the `400` status
  - removed the optional property `fields` from the response with the `401` status
  - removed the optional property `fields` from the response with the `403` status
  - removed the optional property `fields` from the response with the `404` status
  - removed the optional property `fields` from the response with the `409` status
  - removed the optional property `request_id` from the response with the `400` status
  - removed the optional property `request_id` from the response with the `401` status
  - removed the optional property `request_id` from the response with the `403` status
  - removed the optional property `request_id` from the response with the `404` status
  - removed the optional property `request_id` from the response with the `409` status
- **2026-08-19** `b38f8e603649` — 5 breaking, 20 info
  - the `detail` response's property type/format changed from ``/`` to `string`/`` for status `400`
  - the `detail` response's property type/format changed from ``/`` to `string`/`` for status `401`
  - the `detail` response's property type/format changed from ``/`` to `string`/`` for status `403`
  - the `detail` response's property type/format changed from ``/`` to `string`/`` for status `404`
  - the `detail` response's property type/format changed from ``/`` to `string`/`` for status `409`
  - added the optional property `code` to the response with the `400` status
  - added the optional property `code` to the response with the `401` status
  - added the optional property `code` to the response with the `403` status
  - added the optional property `code` to the response with the `404` status
  - added the optional property `code` to the response with the `409` status
  - added the optional property `fields` to the response with the `400` status
  - added the optional property `fields` to the response with the `401` status
  - added the optional property `fields` to the response with the `403` status
  - added the optional property `fields` to the response with the `404` status
  - added the optional property `fields` to the response with the `409` status
  - added the optional property `request_id` to the response with the `400` status
  - added the optional property `request_id` to the response with the `401` status
  - added the optional property `request_id` to the response with the `403` status
  - added the optional property `request_id` to the response with the `404` status
  - added the optional property `request_id` to the response with the `409` status
  - the response property `detail` became required for the status `400`
  - the response property `detail` became required for the status `401`
  - the response property `detail` became required for the status `403`
  - the response property `detail` became required for the status `404`
  - the response property `detail` became required for the status `409`

---

[Operation](https://skmtc.dev/crosmos/apis/crosmos-api/docs/api/v1/orgs/:org_uuid/visibility/settings/patch.md) · [API](https://skmtc.dev/crosmos/apis/crosmos-api.md) · [Page](https://skmtc.dev/crosmos/apis/crosmos-api/changes/api/v1/orgs/:org_uuid/visibility/settings/patch)