---
title: "Delete a specific block"
method: DELETE
path: "/booking/v0-nsfw/blocks/{id}"
tags: ["Block"]
---

# Delete a specific block

`DELETE /booking/v0-nsfw/blocks/{id}`

## Request

- Base URL: `https://api.apaleo.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.apaleo.com/booking/v0-nsfw/blocks/{id}`
- Auth: OAuth 2
  - Implicit: `https://identity.apaleo.com/connect/authorize`
  - Scopes: `blocks.manage`, `reservations.manage`, `admin`

Use this call to delete a block. This is only possible as long as no reservation was picked up yet even if all of
them are canceled<br>You must have at least one of these scopes: 'blocks.manage, reservations.manage'.<br>For fine-grained clients, you must have this permission: 'core.blocks.delete'.

## Path parameters

- `id` string, required

## Response `204`

Deletion of the block was successful.

## Other responses

- `400`: Bad request.
- `401`: You are unauthorized.
- `403`: Forbidden.
- `404`: The Request-URI could not be found.
- `422`: Validation errors in the request body or query params.
- `499`: Client closed request.
- `500`: An unexpected error occurred.
- `503`: The server is currently unavailable. Please try later.

---

[API](https://skmtc.dev/apaleo/apis/apaleo-booking-api-not-safe-for-work.md) - [All operations](https://skmtc.dev/apaleo/apis/apaleo-booking-api-not-safe-for-work/llms.txt) - [OpenAPI document](https://skmtc.dev/apaleo/apis/apaleo-booking-api-not-safe-for-work/revisions/a1b6a2f6b879?raw)