> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daysync.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Field Reference
> Reference tables for the numeric IDs and enum values used across the Daysync Integration API.
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`.
| ID | Type | Notes |
| -- | ------------- | -------------------------- |
| 1 | Schedule Item | Default (non-travel) type |
| 2 | Drive Item | Travel — requires `origin` |
| 3 | Flight Item | Travel — requires `origin` |
| 4 | Rail Item | Travel — requires `origin` |
| 5 | Walk Item | Travel — requires `origin` |
| 6 | Boat Item | Travel — 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`.
| ID | Type | Meaning |
| -- | ----------------------- | --------------------- |
| 1 | `day_of` | The item's own day |
| 2 | `day_before` | The day before (−1) |
| 3 | `day_after` | The next day (+1) |
| 4 | `day_after_after` | Two days later (+2) |
| 5 | `day_after_after_after` | Three days later (+3) |
### Item colors (`itemColorId`)
*Confirmed (1–20).* Colors follow a Tailwind-style palette.
| ID | Color | ID | Color |
| -- | ------- | -- | ------- |
| 1 | gray | 11 | red \* |
| 2 | red | 12 | sky |
| 3 | orange | 13 | blue |
| 4 | amber | 14 | indigo |
| 5 | yellow | 15 | violet |
| 6 | lime | 16 | purple |
| 7 | green | 17 | fuchsia |
| 8 | emerald | 18 | pink |
| 9 | teal | 19 | rose |
| 10 | cyan | 20 | neutral |
\* 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).
| ID | Type |
| -- | ----------- |
| 1 | Confirmed |
| 2 | Unconfirmed |
| 3 | No 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.
| ID | Type | Meaning |
| -- | -------------- | --------------------------- |
| 1 | `mins_before` | `duration` = minutes before |
| 2 | `hours_before` | `duration` = hours before |
| 3 | `days_before` | `duration` = 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.
| ID | Type | ID | Type |
| -- | ---------- | -- | ---------------- |
| 1 | Car | 7 | Van |
| 2 | Commercial | 8 | Ride Share |
| 3 | Private | 9 | Truck |
| 4 | Bus | 10 | Limo |
| 5 | Taxi | 11 | Private Transfer |
| 6 | Charter | | |
## 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.
| ID | Method |
| -- | ---------------- |
| 1 | Will Call |
| 2 | Hotel Delivery |
| 3 | Venue guest list |
| 4 | Tour Manager |
### Statuses (`statusId`)
*Confirmed.*
| ID | Status | Label |
| -- | ------------ | ---------- |
| 1 | `approved` | Approved |
| 2 | `requested` | Requested |
| 3 | `denied` | Denied |
| 4 | `waitlisted` | Waitlisted |
## Venues
### Venue types (`venueTypeId`)
*Confirmed (1–32).*
| ID | Type | ID | Type |
| -- | ----------------- | -- | ---------------- |
| 1 | Hotel | 17 | Fieldhouse |
| 2 | – \* | 18 | Gymnasium |
| 3 | Arena | 19 | Hall |
| 4 | Auditorium | 20 | Other |
| 5 | Ballroom | 21 | Park |
| 6 | Bar | 22 | Radio Station |
| 7 | Cafeteria | 23 | Record Store |
| 8 | Casino | 24 | Rehearsal Studio |
| 9 | Church | 25 | Restaurant |
| 10 | Club | 26 | Shed |
| 11 | Coffeehouse | 27 | Sports Arena |
| 12 | Conference Rooms | 28 | Stadium |
| 13 | Convention Center | 29 | Studio |
| 14 | Fair Ground | 30 | TV Station |
| 15 | Festival Venue | 31 | Tent |
| 16 | Field | 32 | Theatre |
\* ID `2` returns an empty label (`-`) — a deprecated/placeholder row
### Age restrictions (`ageRestrictionId`)
*Confirmed (from backend seed data).*
| ID | Label |
| -- | -------- |
| 1 | All Ages |
| 2 | 16+ |
| 3 | 18+ |
| 4 | 21+ |
### 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.
| ID | Category |
| -- | ---------- |
| 1 | commercial |
| 2 | private |
## Accommodation
### Types (`type`)
| Value | Description |
| ----------- | ----------------- |
| `HOTEL` | Hotel stay |
| `RENTAL` | Rental property |
| `RESIDENCE` | Private residence |
## Shared
### Avatar colors (`avatarColorId`)
*Confirmed (from backend seed data).* Used on tour create (`avatarColorId`) and guest list entries. Identical palette to [Item colors](#item-colors-itemcolorid), including the duplicate `red` at ID 11.
| ID | Color | ID | Color |
| -- | ------- | -- | ------- |
| 1 | gray | 11 | red \* |
| 2 | red | 12 | sky |
| 3 | orange | 13 | blue |
| 4 | amber | 14 | indigo |
| 5 | yellow | 15 | violet |
| 6 | lime | 16 | purple |
| 7 | green | 17 | fuchsia |
| 8 | emerald | 18 | pink |
| 9 | teal | 19 | rose |
| 10 | cyan | 20 | neutral |
## 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:
| ID | Role | Description |
| -- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | `org_admin` | Full access: create, edit, and delete tours, and edit organization information. |
| 2 | `tour_admin` | Can 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. |
| 3 | `tour_member` | Tour-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.