APapaleo
BlockActions

Apply the optional cutoff behavior for a block whose cutoff has been reached.

Internal callback the scheduler invokes when an 'Optional' block's cutoff timer fires. Depending on the block's stored cutoff behavior, this either releases the block ('Optional' to 'Tentative') or leaves it untouched. A stale fire - the block already left 'Optional', or its stored cutoff no longer matches the payload - is a no-op.<br>You must have at least one of these scopes: 'blocks.manage, reservations.manage'.

put/booking/v0-nsfw/block-actions/{id}/cutoff-optional

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/block-actions/{id}/cutoff-optional
  • Auth
    OAuth 2
    Implicit: https://identity.apaleo.com/connect/authorize
    Scopes: blocks.manage, reservations.manage, admin

Path parameters

idstring required

Id of the block that should be processed.

Request body

expectedOptionalCutoffUtcstring date-time required

The optional cutoff timestamp the scheduler fired for. It is compared against the block's stored optional cutoff so a stale or replayed callback (the cutoff was moved, or the block already left 'Optional') is ignored.<br />A date and time in UTC or with UTC offset as defined in <a href="https://en.wikipedia.org/wiki/ISO_8601">ISO8601:2004</a>

Response

The callback was applied, or was a no-op for a stale fire.

Changes

No operation changes recorded.