---
title: "Bulk update memberships"
method: PUT
path: "/membership/"
tags: ["memberships"]
---

# Bulk update memberships

`PUT /membership/`

Any field that can be updated on a membership individually can also be used to bulk update multiple memberships. Pass the comma-separated ids of the memberships to update into `id__in` in `_params`. For example:

```json
{"_params": {"id__in": "memb_A,memb_B"}, "role_id": "role_y6eLquXvRUdmwqi61tsmgCJUU7uGfxaRbDuLoONZL9p"}
```

## Request body

- Membership — Editable settings for an organization membership.
  - `auto_record_calls` 'enabled' | 'disabled' | 'unset'
  - `default_caller_id` string, nullable — ID of the phone number to use as this member's default outbound caller ID.
  - `hangup_recording_url` string, nullable — URL of the audio file used as this member's voicemail drop recording.
  - `may_workflows_impersonate` boolean — Whether Workflows may send emails on this member's behalf.
  - `role_id` string — One of `admin`, `superuser`, `user`, or `restricteduser` for the corresponding predefined role, or the ID of a custom [Role](https://developer.close.com/api/resources/roles).
  - `track_email_opens` boolean — Whether email opens are tracked for emails this member sends.

## Response `200`

Successful response

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `404` — Not found

---

[API](https://skmtc.net/close/apis/close-api.md) · [All operations](https://skmtc.net/close/apis/close-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/close/close-api/revisions/0dcf3303e9d7/schema)