Skip to main content
Many endpoints accept numeric IDs (startTimeTypeId, itemColorId, statusId, pickupMethodId, venueTypeId, and so on) or string enums. This page collects the valid values.
Unless noted otherwise, the values below were verified against the live API by creating records across each ID range and reading back the resolved labels. Items the API does not expose are marked Not verifiable via the API and need backend confirmation.

Schedule

Item types (type)

Confirmed. Types 2–6 are travel items and require an origin.
IDTypeNotes
1Schedule ItemDefault (non-travel) type
2Drive ItemTravel — requires origin
3Flight ItemTravel — requires origin
4Rail ItemTravel — requires origin
5Walk ItemTravel — requires origin
6Boat ItemTravel — requires origin

Time types (startTimeTypeId / endTimeTypeId)

Confirmed. The time type anchors the time to a day relative to the schedule item’s own day — e.g. a “lobby call tomorrow” line shown on today’s day uses day_after.
IDTypeMeaning
1day_ofThe item’s own day
2day_beforeThe day before (−1)
3day_afterThe next day (+1)
4day_after_afterTwo days later (+2)
5day_after_after_afterThree days later (+3)

Item colors (itemColorId)

Confirmed (1–20). Colors follow a Tailwind-style palette.
IDColorIDColor
1gray11red *
2red12sky
3orange13blue
4amber14indigo
5yellow15violet
6lime16purple
7green17fuchsia
8emerald18pink
9teal19rose
10cyan20neutral
* ID 11 resolves to red (a duplicate of 2) — likely a seed-data quirk (TO BE FIXED).

Status types (statusTypeId)

Confirmed. The same values apply to the venue statusTypeId field (both resolve against the same backend table).
IDType
1Confirmed
2Unconfirmed
3No Status

Reminder types (reminder[].typeId)

Confirmed (from backend seed data). The reminder’s duration is a count of the chosen unit — e.g. { "typeId": 2, "duration": 3 } fires 3 hours before the item.
IDTypeMeaning
1mins_beforeduration = minutes before
2hours_beforeduration = hours before
3days_beforeduration = days before

Travel types (traveltype)

Confirmed (from backend seed data). The travel mode for travel items (item types 2–6) — distinct from the item type itself.
IDTypeIDType
1Car7Van
2Commercial8Ride Share
3Private9Truck
4Bus10Limo
5Taxi11Private Transfer
6Charter

Guest list

Pickup methods (pickupMethodId)

Confirmed (from backend seed data). Required when adding a guest. Note: the guest-list GET response does not return the pickup method, so the value cannot be read back through the API.
IDMethod
1Will Call
2Hotel Delivery
3Venue guest list
4Tour Manager

Statuses (statusId)

Confirmed.
IDStatusLabel
1approvedApproved
2requestedRequested
3deniedDenied
4waitlistedWaitlisted

Venues

Venue types (venueTypeId)

Confirmed (1–32).
IDTypeIDType
1Hotel17Fieldhouse
2– *18Gymnasium
3Arena19Hall
4Auditorium20Other
5Ballroom21Park
6Bar22Radio Station
7Cafeteria23Record Store
8Casino24Rehearsal Studio
9Church25Restaurant
10Club26Shed
11Coffeehouse27Sports Arena
12Conference Rooms28Stadium
13Convention Center29Studio
14Fair Ground30TV Station
15Festival Venue31Tent
16Field32Theatre
* ID 2 returns an empty label (-) — a deprecated/placeholder row

Age restrictions (ageRestrictionId)

Confirmed (from backend seed data).
IDLabel
1All Ages
216+
318+
421+

Venue categories (venueCategoryId)

Confirmed. A valid venueCategoryId is required to create a venue — omitting it or sending an unknown ID causes the create to fail.
IDCategory
1commercial
2private

Accommodation

Types (type)

ValueDescription
HOTELHotel stay
RENTALRental property
RESIDENCEPrivate residence

Shared

Avatar colors (avatarColorId)

Confirmed (from backend seed data). Used on tour create (avatarColorId) and guest list entries. Identical palette to Item colors, including the duplicate red at ID 11.
IDColorIDColor
1gray11red *
2red12sky
3orange13blue
4amber14indigo
5yellow15violet
6lime16purple
7green17fuchsia
8emerald18pink
9teal19rose
10cyan20neutral

User & organization roles

Confirmed (from backend seed data). Role IDs/names appear under several keys (loggedInUserRole, user_role_type, user_role) and the naming varies by context, but the underlying IDs are:
IDRoleDescription
1org_adminFull access: create, edit, and delete tours, and edit organization information.
2tour_adminCan create and edit the entities inside a tour (schedule items, venues, accommodation, guest list, bulletins). Cannot create new tours, and cannot edit the tour’s own details or organization information.
3tour_memberTour-level role scoped to the entities inside a tour; cannot create or edit tours, or edit organization information.
Only org_admin can create or edit tours and edit organization information. tour_admin and tour_member operate only on the entities inside a tour — schedule items, venues, accommodation, guest list, and bulletins — not on the tour record itself or on org settings.