> For the complete documentation index, see [llms.txt](https://docs.vomevolunteer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vomevolunteer.com/resources/schedule/shift-series/write-operations/remove-users-from-a-shift-series.md).

# Remove users from a shift series

Takes volunteers off a series. Future shift enrollments are dropped and the series membership is closed.

**Past attendance is always kept.** Shifts the volunteer already worked, and the hours they logged, are untouched. Removing somebody from a series is not a way to erase their history.

#### Endpoint

`POST /api/shift-series/bulk-remove/`

### Fields

| Field            | Required       | Description                                                                                                                                                                  |
| ---------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `series_id`      | Yes            | The series to remove them from.                                                                                                                                              |
| `user_ids`       | One of the two | The volunteers. Resolved to their enrollments for you.                                                                                                                       |
| `enrollment_ids` | One of the two | The enrollments directly, as [List series attendees](https://docs.vomevolunteer.com/resources/schedule/shift-series/write-operations/list-series-attendees.md) returns them. |

Send whichever you have. An integration usually knows the volunteer rather than the enrollment row, so `user_ids` is normally the easier one.

#### Payload sample

```json
{
  "series_id": "7c0f3f20-6e39-4b80-bb35-7d743f0193a6",
  "user_ids": ["4a17144c-58c8-4103-8c0a-f2ac12079e7a"]
}
```

#### Response sample

```json
{
  "success": true,
  "processed": 1,
  "removed": [
    {
      "enrollment_id": "3b4e9461-8b34-4d5b-9c3d-48f6f85f0f01",
      "left_at": "2026-10-08T02:30:00Z",
      "future_shift_enrollments_deleted": 48
    }
  ],
  "errors": {}
}
```

### Users who are not on the series

A user who is not currently on the series is reported in `errors` rather than passing silently, so a sync does not quietly believe it removed somebody it never found.

```json
{
  "success": false,
  "processed": 0,
  "removed": [],
  "errors": {
    "user_ids": ["Not currently on this series: 4a17144c-58c8-4103-8c0a-f2ac12079e7a."]
  }
}
```
