/reservations/seats/:id

Updates a seat reservation

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Reservations may not overlap with existing reservations for the same seat. Each reservation type has different use-cases and rules:

  • ~~assigned~~An assigned seat. Optionally may have no end date, representing a permanent assignment. Deprecated, use /seats/:id/publish-shared-schedule
  • hot An ad-hoc, single-day booking. Must have an end time that is the same calendar day as the start time.
  • hoteled A reservation booked in advance that can be multi-day. Must have an end time.
  • reverse_hotel A reservation that is an exclusion for recurring reservations types such as assigned orshared. These reservations can be made on days when recurring reservations were freed up or shared.
  • shareduse /seats/:id/publish-shared-schedule
Path Params
int32
required

The ID of the reservation to update

Body Params
string

A title for the reservation.

start
object

A composite datetime / timezone object that represents the start of the reservation.

end
object

A composite datetime / timezone object that represents the start of the reservation. When not given, the reservation is considered to have no end date. This is required for hot and hoteled reservations.

recurrence
array of strings

An array RFC-5545 compliant content-lines that are of the type RRULE, RDATE, and EXDATE.

recurrence
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json