---
title: "Changes to List organization members"
method: GET
path: "/v2/organizations/{organization_id}/access/members"
---

# Changes to List organization members

`GET /v2/organizations/{organization_id}/access/members`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 2 of 13 revisions.

- **2026-09-09** `217c96dc9a29` — 26 breaking, 158 info
- **2026-09-02** `e04f76c478af` — 2 info

## Changes

- **2026-09-09** `217c96dc9a29` — 26 breaking, 158 info
  - the `code` response's property type changed from `string` to no type for status `403`
  - the `code` response's property type changed from `string` to no type for status `404`
  - the `code` response's property type changed from `string` to no type for status `429`
  - the `code` response's property type changed from `string` to no type for status `500`
  - the `code` response's property type changed from `string` to no type for status `503`
  - the `doc_url` response's property type changed from `string` to no type for status `403`
  - the `doc_url` response's property type changed from `string` to no type for status `404`
  - the `message` response's property type changed from `string` to no type for status `404`
  - the `message` response's property type changed from `string` to no type for status `429`
  - the `message` response's property type changed from `string` to no type for status `500`
  - the `message` response's property type changed from `string` to no type for status `503`
  - the `operation` response's property type changed from `string` to no type for status `503`
  - the `param` response's property type changed from `string` to no type for status `404`
  - the `provider` response's property type changed from `string` to no type for status `503`
  - the `required_scope` response's property type changed from `string` to no type for status `403`
  - the `resource_id` response's property type changed from `string` to no type for status `404`
  - the `resource_type` response's property type changed from `string` to no type for status `404`
  - the `retry_after` response's property type changed from `number` to no type for status `429`
  - the `type` response's property type changed from `string` to no type for status `403`
  - the `type` response's property type changed from `string` to no type for status `404`
  - the `type` response's property type changed from `string` to no type for status `429`
  - the `type` response's property type changed from `string` to no type for status `500`
  - the `type` response's property type changed from `string` to no type for status `503`
  - the `upstream_code` response's property type changed from `string` to no type for status `503`
  - the `upstream_message` response's property type changed from `string` to no type for status `503`
  - the `upstream_status` response's property type changed from `number` to no type for status `503`
  - added `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5` to the response body `anyOf` list for the response status `401`
  - added `subschema #2` to the response body `anyOf` list for the response status `400`
  - removed `subschema #1: Missing API Key, subschema #2: Invalid API Key Format, subschema #3: Invalid API Key, subschema #4: Authentication Failed, subschema #5: Invalid Session` from the response body `anyOf` list for the response status `401`
  - removed `subschema #2: Bad Request` from the response body `anyOf` list for the response status `400`
  - added `subschema #1` to the `cause` response property `anyOf` list for the response status `500`
  - added `subschema #1` to the `code` response property `anyOf` list for the response status `403`
  - added `subschema #1` to the `code` response property `anyOf` list for the response status `404`
  - added `subschema #1` to the `code` response property `anyOf` list for the response status `429`
  - added `subschema #1` to the `code` response property `anyOf` list for the response status `500`
  - added `subschema #1` to the `code` response property `anyOf` list for the response status `503`
  - added `subschema #1` to the `data/items/membership_id` response property `anyOf` list for the response status `200`
  - added `subschema #1` to the `doc_url` response property `anyOf` list for the response status `403`
  - added `subschema #1` to the `doc_url` response property `anyOf` list for the response status `404`
  - added `subschema #1` to the `message` response property `anyOf` list for the response status `404`
  - …144 more
  - …this revision’s changelog is incomplete
- **2026-09-02** `e04f76c478af` — 2 info
  - added the non-success response with the status `503`
  - removed the non-success response with the status `502`

---

[Operation](https://skmtc.dev/superwall/apis/superwall-api-v2/docs/v2/organizations/:organization_id/access/members/get.md) · [API](https://skmtc.dev/superwall/apis/superwall-api-v2.md) · [Page](https://skmtc.dev/superwall/apis/superwall-api-v2/changes/v2/organizations/:organization_id/access/members/get)