---
title: "Delete booking anchor"
method: DELETE
path: "/booking_anchors/{id}"
tags: ["Booking - Anchors"]
---

# Delete booking anchor

`DELETE /booking_anchors/{id}`

## Request

- Base URL: `https://api.jammed.app/api/v2`
- URL: `https://api.jammed.app/api/v2/booking_anchors/{id}`
- Auth: none declared. Required headers: `Authorization`

Delete any booking anchor, whatever its source. Deleting an `auto` anchor reopens that day for its room, but Jammed recreates it the next time it syncs anchors from that booking (for example when the booking changes), as it does in the admin.

There is no update endpoint: to move an anchor, delete it and create a new one.

Requires the `bookings.write` scope when using OAuth tokens.

## Path parameters

- `id` integer, required

## Headers

- `Authorization` string, required

## Response `200`

Booking anchor deleted

- StatusResponse
  - `status` 'ok' | 'error'
  - `message` string

## Other responses

- `401`: Unauthorized - Invalid API key
- `403`: Forbidden - the OAuth token lacks the scope, or does not belong to an admin
- `404`: Not found - the booking anchor does not exist
- `422`: Unprocessable - sticky bookings are not turned on

## Changes

- **2026-11-05** (v2) `d512cbbe42fb`: 2 info
  - api tag `Booking - Anchors` added
  - api tag `Booking Anchor Endpoints` removed
- **2026-10-19** (v2) `c8d56b30958a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/jammed-org/apis/jammed-bookings-api/changes/booking_anchors/:id/delete.md)

---

[API](https://skmtc.dev/jammed-org/apis/jammed-bookings-api.md) - [All operations](https://skmtc.dev/jammed-org/apis/jammed-bookings-api/llms.txt) - [OpenAPI document](https://skmtc.dev/jammed-org/apis/jammed-bookings-api/revisions/d512cbbe42fb?raw)