Skip to main content
Guest list entries are the people requested onto the list for a given tour day, with pass allocations and an approval status. Guest list entry IDs are integers. All endpoints require the standard authentication headers.

​
List guest list

GET /v1/tours/{tourId}/days/{dayId}/guestlist
Returns the guest list for one day of a tour. Scope: guestlist.read Example 
curl "$BASE/v1/tours/2f1c…/days/1843/guestlist" \
  -H "x-api-key: $KEY" -H "x-api-secret: $SECRET" -H "Authorization: Bearer $TOKEN"
Path parameters
NameTypeDescription
tourIdstring (UUID)The tour.
dayIdintegerThe day within the tour.
Response data — array of guest list entries: 
{
  "id": 77,
  "firstName": "Sam",
  "lastName": "Taylor",
  "email": "sam@…",
  "affiliation": "Press",
  "numberOfGuests": 2,
  "notes": "Photo pit access",
  "status": { "id": 1, "type": "APPROVED", "description": "Approved" },
  "created_by": { "id": "…", "firstname": "Jane", "lastname": "Doe" },
  "day": { "id": 1843, "name": "Day 1", "date": "2026-06-01T00:00:00Z" },
  "tour": { "id": "2f1c…", "name": "Spring Tour 2026" },
  "is_deleted": false,
  "created_at": "2026-05-18T08:00:00Z",
  "updated_at": "2026-05-20T08:00:00Z"
}
Response fields — the GET response returns a fixed subset of fields, which differs from what create/edit accept. It does not include passes, pickupMethod, venue, or avatarColor:
FieldTypeDescription
idintegerGuest list entry ID.
firstNamestringGuest first name.
lastNamestringGuest last name.
emailstringGuest email (may be null).
affiliationstringGuest affiliation (may be null).
numberOfGuestsintegerParty size.
notesstringNotes (may be null).
statusobject{ id, type, description }.
created_byobject{ id, firstname, lastname }.
dayobject{ id, name, date }.
tourobject{ id, name }.
is_deletedbooleanSoft-delete flag.
created_atstringISO 8601 timestamp.
updated_atstringISO 8601 timestamp.

​
Add to guest list

POST /v1/guestlist
Scope: guestlist.write Body
FieldTypeRequiredDescription
tour_idstring (UUID)YesTour the entry belongs to.
day_idnumberYesDay the entry is for.
firstNamestringYesGuest first name.
lastNamestringYesGuest last name.
numberOfGuestsnumberYesParty size.
pickupMethodIdnumberYesHow the guest collects passes — valid values.
statusIdnumberYesApproval status — valid values.
passesarray<Pass>YesPass allocations — see Pass object.
emailstringNoGuest email.
affiliationstringNoGuest affiliation.
notesstringNoFree-text notes.
requesterIdstringNoWho requested the entry.
venueIdnumberNoAssociated venue.
avatarColorIdnumberNoAvatar colour — valid values.
Response data: { "id": 77 }.

​
Edit a guest list entry

PUT /v1/guestlist/{guestListId}
Scope: guestlist.write Path parameters
NameTypeDescription
guestListIdintegerThe entry to edit.
Body — note several fields remain required on edit:
FieldTypeRequiredDescription
firstNamestringYesGuest first name.
lastNamestringYesGuest last name.
numberOfGuestsnumberYesParty size.
pickupMethodIdnumberYesPickup method — valid values.
statusIdnumberYesApproval status — valid values.
passesarray<Pass>YesPass allocations — see Pass object.
email, affiliation, notes, requesterId, venueId—NoAs in create.
The guestListId is taken from the URL path — do not send it in the request body.
Response data: { "id": 77 }.

​
Pass object

Each entry in the passes array allocates a number of passes of a given pass type to the guest. Pass types are configured per tour in the Daysync app. 
"passes": [
  { "passId": 1, "count": 2 },
  { "passId": 3, "count": 1 }
]
FieldTypeRequiredDescription
passIdnumberYesID of the pass type configured for this tour.
countnumberYesNumber of passes of this type to allocate to the guest.
Pass type IDs are configured per tour in the Daysync app. Discover the valid IDs from the tour/venue configuration in the app before sending them on create or edit.

​
Delete a guest list entry

DELETE /v1/guestlist/{guestListId}
Scope: guestlist.write Path parameters
NameTypeDescription
guestListIdintegerThe entry to delete.
Response data: none.
See also: Tours, Bulletins.