> 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/change-when-a-series-ends.md).

# Change when a series ends

Moves a series' end date in either direction. Use this to extend a series that is about to run out, to finish one early, or to remove the end date entirely.

#### Endpoint

`POST /api/shift-series/{series_id}/reschedule-end/`

### Send exactly one intent

| What you send                                            | What happens                                                                                                                |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| `end_date` (or `ends_at`) **later** than the current end | The series extends, and Vome generates the newly opened window straight away. Silent: nobody is notified about more shifts. |
| `end_date` (or `ends_at`) **earlier**                    | The series is brought in. Shifts past the new end are cancelled when `cancel_future_shifts` is true.                        |
| `make_open_ended: true`                                  | The end date is removed and the series runs indefinitely.                                                                   |

| Field                  | Default | Notes                                   |
| ---------------------- | ------- | --------------------------------------- |
| `cancel_future_shifts` | `true`  | Only applies when bringing a series in. |
| `notify_users`         | `false` | Only applies when bringing a series in. |
| `message`              |         | A note for that notification.           |

Notifications only apply when shortening because that is the only direction where people lose shifts they were booked onto. Extending gives people more, so it says nothing.

#### Payload samples

Extend to the end of next year:

```json
{ "end_date": "2027-12-31" }
```

Remove the end date:

```json
{ "make_open_ended": true }
```

Finish early and tell everyone affected:

```json
{
  "end_date": "2026-12-20",
  "cancel_future_shifts": true,
  "notify_users": true,
  "message": "The program pauses over the holidays."
}
```

#### Response sample

```json
{
  "series_id": "7c0f3f20-6e39-4b80-bb35-7d743f0193a6",
  "direction": "grow",
  "ends_at": "2027-12-31T23:59:59Z",
  "shifts_created": 34,
  "shifts_cancelled": 0,
  "queued": false
}
```

`direction` is `grow`, `shrink` or `noop`, worked out from the dates rather than from what you asked for, so you can confirm the effect. A large extension is queued and returns `"queued": true`.

### Reopening an ended series

Extending works on a series that has already ended. It goes back to active and starts generating again, which is the way to undo an end that was a mistake.
