Daysync Integration API - 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?

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	What the API is, base URL, request/response conventions, identifiers, dates.
Quickstart	Make your first call and walk a read → write flow.
Authentication	The dual auth model (partner key/secret + user OAuth token) and the OAuth flow.
Scopes & Permissions	Every scope, the scope each endpoint needs, partner vs. user permissions.
Errors	Error envelope, status codes, and the business rules (subscription, soft-delete, validation).

Endpoint reference

Resource	Endpoints
Organizations	List organizations, members, and the key-contact book (read-only).
Tours	List, create, edit, delete tours; list tour members; load a whole tour in one call; render a day sheet PDF.
Schedule	List, create, update, delete schedule items; batch create; confirm a whole day.
Schedule Templates	Save a set of items as a reusable template, then apply it to another day.
Venues	List, get, create, update, delete venues.
Accommodation	List, get, create, edit, delete stays.
Rooms	Rooms within a stay, and who is in them.
Guest List	List, add, edit, delete guest list entries.
Bulletins	List, create, update, delete bulletins.
Chat	Read channel and group-chat history. Read-only; no direct messages.
Tags	Create and manage the tags that label schedule items.
Custom Fields	Extra fields on schedule items, venues, and stays.
Contacts	The organization contact book, and contacts on venues and stays.
Attachments	Upload a file (URL, inline bytes, or a signed ticket), attach it, list a tour’s files, and download one.
Reference Data	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.

New to the API? Two calls do most of the discovery work: GET /v1/reference/types for the ID lookups every write needs, and GET /v1/tours/{tourId}/data to load a whole tour in one request instead of paging resource by resource.