---
title: "Clear unavailability for a day on an offering"
method: POST
path: "/shop/offering-availability/remove-day-unavailability"
tags: ["OfferingAvailability"]
---

# Clear unavailability for a day on an offering

`POST /shop/offering-availability/remove-day-unavailability`

Removes every `unavailable` availability rule that covers the
targeted day on the offering. If a rule spans more than the
targeted day (e.g. a multi-day block), it is split into
surrounding rules that preserve the unavailability on the days
that weren't targeted.

The operation is serialised via a per-offering lock to prevent
concurrent edits clobbering each other; if another request is
currently modifying the same offering, the call returns `429 Too
Many Requests`.

Requires the `SETTINGS_MANAGE` permission on the offering's site.

## Request body

- object
  - `date` string, date, required — ISO 8601 calendar date to mark unavailable, in the offering's timezone.
  - `offering_type` 'appointment' | 'area_booking' | 'package' | 'session', required — The offering type the `offering_id` belongs to.
  - `offering_id` string, required — ID of the offering to update.

## Response `204`

The day's unavailability rules were successfully cleared.

## Other responses

- `401` — The user is unauthenticated
- `403` — The authenticated user does not have permission.
- `404` — The resource couldn't be found
- `422` — The request didn't pass validation
- `429` — Another request is currently modifying availability rules for this offering. Retry after a short backoff.

---

[API](https://skmtc.dev/try/apis/trybe-api.md) · [All operations](https://skmtc.dev/try/apis/trybe-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/try/trybe-api/revisions/f37f92702da5/schema)