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

# Daysync Integration API

> Partner-facing documentation for the Daysync Integration API.

The Daysync Integration API lets approved partner applications read and write tour data on behalf of a Daysync user — tours, schedules, venues, accommodation, rooms, guest lists, bulletins, tags, custom fields, contacts, and read-only chat history.

The production base URL is `https://integration.daysync.com`; all endpoints are versioned under `/v1`.

> **[Prefer to skip the code?](https://docs.daysync.com/mcp/overview.md)**
>
> Daysync runs a hosted **MCP server**. Connect it to Claude or ChatGPT and work with your tours in plain language — no integration to build.

## Getting started

| Page | What it covers |
| - | - |
| [Introduction](https://docs.daysync.com/introduction.md) | What the API is, base URL, request/response conventions, identifiers, dates. |
| [Quickstart](https://docs.daysync.com/quickstart.md) | Make your first call and walk a read → write flow. |
| [Authentication](https://docs.daysync.com/authentication.md) | The dual auth model (partner key/secret + user OAuth token) and the OAuth flow. |
| [Scopes & Permissions](https://docs.daysync.com/scopes.md) | Every scope, the scope each endpoint needs, partner vs. user permissions. |
| [Errors](https://docs.daysync.com/errors.md) | Error envelope, status codes, and the business rules (subscription, soft-delete, validation). |

## Endpoint reference

| Resource | Endpoints |
| - | - |
| [Organizations](https://docs.daysync.com/endpoints/organizations.md) | List organizations, members, and the key-contact book (read-only). |
| [Tours](https://docs.daysync.com/endpoints/tours.md) | List, create, edit, delete tours; list tour members; load a whole tour in one call; render a day sheet PDF. |
| [Schedule](https://docs.daysync.com/endpoints/schedule.md) | List, create, update, delete schedule items; batch create; confirm a whole day. |
| [Schedule Templates](https://docs.daysync.com/endpoints/schedule-templates.md) | Save a set of items as a reusable template, then apply it to another day. |
| [Venues](https://docs.daysync.com/endpoints/venues.md) | List, get, create, update, delete venues. |
| [Accommodation](https://docs.daysync.com/endpoints/accommodation.md) | List, get, create, edit, delete stays. |
| [Rooms](https://docs.daysync.com/endpoints/rooms.md) | Rooms within a stay, and who is in them. |
| [Guest List](https://docs.daysync.com/endpoints/guest-list.md) | List, add, edit, delete guest list entries. |
| [Bulletins](https://docs.daysync.com/endpoints/bulletins.md) | List, create, update, delete bulletins. |
| [Chat](https://docs.daysync.com/endpoints/chat.md) | Read channel and group-chat history. Read-only; no direct messages. |
| [Tags](https://docs.daysync.com/endpoints/tags.md) | Create and manage the tags that label schedule items. |
| [Custom Fields](https://docs.daysync.com/endpoints/custom-fields.md) | Extra fields on schedule items, venues, and stays. |
| [Contacts](https://docs.daysync.com/endpoints/contacts.md) | The organization contact book, and contacts on venues and stays. |
| [Attachments](https://docs.daysync.com/endpoints/attachments.md) | Upload a file (URL, inline bytes, or a signed ticket), attach it, list a tour's files, and download one. |
| [Reference Data](https://docs.daysync.com/endpoints/reference.md) | The ID lookups the write endpoints need. |

## All endpoints at a glance

**102 endpoints** across 15 scopes. The full method-by-method list, with the scope each one requires, is on [Scopes & Permissions](https://docs.daysync.com/scopes.md#scope-per-endpoint).

> [!TIP]
>
> New to the API? Two calls do most of the discovery work: [`GET /v1/reference/types`](https://docs.daysync.com/endpoints/reference) for the ID lookups every write needs, and [`GET /v1/tours/{tourId}/data`](https://docs.daysync.com/endpoints/tours) to load a whole tour in one request instead of paging resource by resource.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.