> ## 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.

# Changelog

> A log of changes to the Daysync Integration API — new endpoints, fields, fixes, and deprecations.

Changes to the Daysync Integration API are listed here, newest first. Partners should watch this page to know when to update their integrations.

<Note>
  This changelog was started on 2026-06-08. Entries below this date are documentation changes; behavioural API changes will be recorded here going forward.
</Note>

## 2026-07-09

**New endpoint**

* Added [`POST /v1/attachments`](/endpoints/attachments) (scope `schedule.write`) — upload a file by URL for attaching to schedule items, venues, accommodation, and guest list entries. Daysync fetches the URL server-side (SSRF-guarded: public https/http only, no redirects, 25 MB, 15 s) and returns a hosted `link` to pass in the `attachment`/`attachments` field. New [Attachments](/endpoints/attachments) page.
* Clarified that `attachment.link` is a **Daysync storage key** (from the upload endpoint), not an external URL — corrected the [Schedule → Attachments](/endpoints/schedule#attachments) guidance and the [Venues](/endpoints/venues#create-a-venue) note.
* Endpoint count is now **29**.

## 2026-06-12

**Documentation**

* Documented [`GET /v1/day-types`](/endpoints/tours#list-day-types) — live since launch but previously missing from the docs. It returns the valid `day_type_id` values required when creating or editing tours.
* New pages: [Apply for API Access](/apply-for-access), [Callback URLs](/callback-urls), and [Environments](/environments).
* Rewrote [Authentication](/authentication) — clarified the two-credential model (shared OAuth Client vs per-partner API keys), added an OAuth error reference, token-type guide (`access_token` vs `id_token` vs `refresh_token`), refresh/revocation behaviour, and JWKS details for server-side validation.
* Rewrote [Quickstart](/quickstart) as an end-to-end walkthrough — from received credentials to a refreshed token in five steps.
* Corrected the endpoint count (28) on the [overview](/) and added the missing scope row on [Scopes & Permissions](/scopes).
* **Destructive-edit warning on [Edit a tour](/endpoints/tours#edit-a-tour)** — `day_list` is declarative: days omitted from the list are permanently deleted along with all their content. Documented the safe single-day update pattern.
* New [Visibility](/endpoints/schedule#visibility) and [Attachments](/endpoints/schedule#attachments) sections on the schedule page — where visibility IDs come from, the omit-everything footgun (`isEveryone` defaults to `false`), conflicting-flag `400`, link-based attachment model, and attachment upsert/delete semantics on update.
* Every numeric type field (`type`, `startTimeTypeId`, `statusTypeId`, `itemColorId`, `venueTypeId`, `pickupMethodId`, …) now links to its [Field Reference](/field-reference) value table.
* Four previously undocumented ID catalogues added to [Field Reference](/field-reference), verified against backend seed data: **reminder types** (`reminder[].typeId`), **travel types** (`traveltype`, 11 modes), **age restrictions** (`ageRestrictionId`), and **avatar colors** (`avatarColorId`). Also noted that venue `statusTypeId` shares the schedule status-type table.
* New [Retries & idempotency](/introduction#retries-and-idempotency) section — per-method retry safety, the `POST`-after-timeout duplicate trap, and which responses are worth retrying.
* New [Data model at a glance](/introduction#data-model-at-a-glance) diagram — the org → tour → day hierarchy, which resources are day-scoped vs tour-scoped, and the ID type at each level.
* Documented the [`/oauth2/userInfo`](/authentication#getting-the-users-profile-oauth2userinfo) endpoint for fetching the connected user's profile without decoding JWTs.
* Marked venue `venueCategoryId` as required-in-practice in the body table (was contradicting the note below it).

## 2026-06-08

**Documentation**

* Added a [Field Reference](/field-reference) page covering schedule item types, accommodation types, and other enum/ID values.
* Documented the [accommodation date/time format](/endpoints/accommodation) (epoch-milliseconds dates and minutes-from-midnight times).
* Added a [Pass object](/endpoints/guest-list#pass-object) reference and a full GET response field table on the guest list endpoint.
* Added a [field-naming convention warning](/introduction#field-naming) (snake\_case vs camelCase).
* Added full error [response body examples](/errors#response-body-examples).
* Added [Common Workflows](/common-workflows) recipes and operational notes (rate limits, versioning, webhooks, pagination).