sessions

Cancel one time and every booking in it; its guests are emailed. With guests: choose, each guest picks another time of the offering (or a refund) on their booking page within 7 days instead. On a time already called off, guests: refund cancels and refunds whoever is still picking; again, it changes nothing

post/sessions/{id}/cancel

Request

  • Base URL: https://daybag.io/api/v1
  • URL: https://daybag.io/api/v1/sessions/{id}/cancel
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Request body

guests'refund' | 'choose'

refund (default): cancel every booking, refunding what was paid online. choose: holds and a reseller's bookings are cancelled; each other booking stays confirmed with choose_by, the end of the 7th day in the org's time zone, while its guest picks another time of the offering (booking.moved) or cancels. Whoever hasn't picked by then is cancelled, refunding what they paid online

notestring

A line in your words for the guests' email, such as why the time can't run

Response

Success

idstring required
org_idstring required
offering_idstring required
starts_atstring required

ISO 8601 timestamp (UTC)

ends_atstring required

ISO 8601 timestamp (UTC)

capacityinteger nullable required

Seats for this session; null means the class's capacity

status'scheduled' | 'cancelled' required
series_idstring nullable

The calendar entry it's a time of; null when scheduled on its own

occurs_onstring nullable

Its entry's local date for it

created_atstring required

ISO 8601 timestamp (UTC)

Changes

No recorded changes to this operation across all 1 revision of this API.