Skip to main content
A stay (accommodation) holds one or more rooms, each with its own check-in/out times, confirmation number, and occupants. Rooms are created under their stay but addressed by their own ID once they exist. All endpoints require the standard authentication headers.

List a stay’s rooms

Scope: accommodation.read Response data — array of room assignments:
users are occupants with a Daysync account; pendingInvites are people invited to the tour who have not accepted yet.

Add a room

Scope: accommodation.write Body
roomType comes from GET /v1/reference/types, group hotelRoomTypes.generalNotes and confirmationNumber are required by the API even when empty — send "" rather than omitting them.All four date/time fields are epoch milliseconds, not ISO strings.
Example
Response data: { "id": 8508, "name": "Tour manager" }

Update a room

Scope: accommodation.write All fields optional — send only what changes.
guestList replaces the room’s occupant list. Include every occupant the room should end up with, not just the one you are adding.
Response data: { "id": 8508, "name": "…" }

Delete a room

Soft-deletes the room. Reversible. Scope: accommodation.write Response data: { "id": 8508, "name": "…" }

Restore a room

Scope: accommodation.write Response data: { "id": 8508, "name": "…" }
Rooms live at /v1/rooms/{id} once created, not under their stay. Only the list and create endpoints are nested under /v1/accommodation/{accommodationId}.

See also: Accommodation, Contacts, Reference Data.