Versioning & changelog
The promise
The version is in the path: /api/v1. Within v1, changes only add — new routes, new optional parameters, new fields in answers, new event types. Write receivers and parsers that ignore what they do not recognise, and nothing we add will break you.
A change that could break working code — removing or renaming a field, a route or an event, or changing what a field means — makes v2. When v2 arrives, v1 keeps working for at least 12 months. During that time its answers carry Deprecation and Sunset headers with the dates, and owners with live tokens are told by email.
One exception, stated plainly: if a field ever has to go to protect people’s privacy or security, it may go within a version, with as much notice as the risk allows.
Support
Write to team@daysli.com with the requestId from the error and the time it happened. Never send a token.
Changelog
v1 — 7 October 2026
- Personal tokens, live and test, with eight scopes.
- Read:
/me,/appointment-types,/availability,/events,/tasks,/requests. - Ask: appointment and to-do requests, and withdrawing them.
- Signed webhooks for requests, to-dos and events, with catch-up.