# Delete a member from an alert list

`DELETE /api/bookings/{memberId}/alert-list`

- **Products:** Operator (`FOH`), Consumer (`CONSUMER`) (any one of these products, not all)
- **Features:** Online Bookings (`ONLINEBOOK`), Front of House Generic Access (`FOHGENERIC`) (any one of these features, not all)

HTML version: [Delete a member from an alert list](https://support.gladstonesoftware.cloud/reference/bookings/delete-a-member-from-an-alert-list)

## Overview

Removes a member's place on the alert list (waiting list) for one booking. An alert list holds members who wanted a place on a class or activity that was full; when a place frees up they can be promoted onto the booking with [Promotes a member from an alert list](promotes-a-member-from-an-alert-list.md).

This endpoint only removes **alert-list** places. If the member holds a confirmed place on the booking rather than an alert-list place, the request fails with `404` and nothing is changed — it is not a way to cancel a booking. Other parts of the platform pick up the removal without further calls from you.

## Endpoint

`DELETE {base_url}/api/bookings/{memberId}/alert-list`

`{base_url}` is the environment URL issued to your integration. See [Authenticating with Gladstone APIs](../../guides/authenticating-with-gladstone-apis.md).

## Path parameters

| Name | Type | Required | Description |
|------|------|----------|-------------|
| `memberId` | integer (int32) | Yes | The member whose alert-list place is removed. Must be a positive integer, otherwise the request fails with `400`. Only this member's place is affected — other members on the same alert list are untouched. |

## Request body

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `bookingId` | integer (int32) | Yes | The booking the member is queuing for — one dated instance of a class or activity, not the activity itself. Must be a positive integer and must already exist, otherwise the request fails. For a class, take this value from the `bookingId` field inside the JSON `slotReferences` string returned by the sessions endpoints, such as [List all available sessions for a specific member](list-all-available-sessions-for-a-specific-member.md). |

## Sample request

```bash title="cURL"
curl -X DELETE '{base_url}/api/bookings/{memberId}/alert-list' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true' \
  -H 'Content-Type: application/json' \
  -d '{
  "bookingId": 12345
}'
```

## Errors

| Status | Meaning | When |
|--------|---------|------|
| `400` | Bad request | `memberId` is not a positive integer (`Invalid MemberId, must be a positive integer`); `bookingId` is not a positive integer (`Invalid BookingId, must be a positive integer`); or the booking does not exist (`Booking ID {bookingId} does not exist`). |
| `404` | Not found | The member has no place at all on this booking, or has a confirmed place rather than an alert-list place: `Member ID {memberId} is not on the alert list for booking {bookingId}`. Repeating a successful call therefore returns `404` the second time. |
| `500` | Internal server error | |