Scopes & permissions
A token can do only what its scopes allow, and the member chose them, in the words in the second column. A missing scope is 403 insufficient_scope, with the scope named in WWW-Authenticate.
| Scope | What the member sees | Routes | Never included |
|---|---|---|---|
profile:read | See your name, username and timezone | Email address, phone, bio, settings. | |
availability:read | See your appointment types and when you’re free | GET /appointment-types GET /availability | Why a time is not free; event titles; which calendar is busy. Nothing while booking is off. |
events:read | See your calendar events and appointments | GET /events GET /events/{id} | Notes, participants, busy time imported from other calendars, repeat rules. |
tasks:read | See your to-dos | GET /tasks GET /tasks/{id} | Requesters’ contact details. |
requests:read | See requests people send you | GET /requests GET /requests/{id} | Requesters’ email, phone and handles (they need requests:contact); the member’s private states. |
requests:contact | See the email and phone number of people who send you requests | Adds contact details to GET /requests | — |
requests:create | Send requests to you, which you accept or decline | POST /requests/appointments POST /requests/tasks POST /requests/{id}/withdraw | Any direct change to the calendar or to-dos; other tokens’ requests. |
webhooks | Be told when these things change | GET /webhook-events GET /webhook-events/{id} GET /webhook-endpoints POST /webhook-endpoints GET /webhook-endpoints/{id} POST /webhook-endpoints/{id} POST /webhook-endpoints/{id}/ping POST /webhook-endpoints/{id}/rotate-secret POST /webhook-endpoints/{id}/delete GET /webhook-endpoints/{id}/deliveries POST /webhook-deliveries/{id}/resend and deliveries | Events for permissions the token does not have. |
public:read | See public pages, company and vessel profiles and Opportunities listings on Daysli | GET /pages/{id} GET /organisations/{id} GET /opportunities GET /opportunities/{id} | Contact details, profile links, photos, anything unpublished, paused, suspended or from a page that is off. |
GET /me works with any valid token. requests:contact goes with requests:read and is refused on its own.
Webhook events by scope
| Scope | Events |
|---|---|
requests:read | request.created request.withdrawn request.accepted request.declined request.expired appointment.rescheduled appointment.confirmed appointment.cancelled appointment.completed |
tasks:read | task.created task.updated task.completed task.deleted |
events:read | event.created event.updated event.deleted |
ping and authorization.revoked reach every address and are not chosen.
Privacy boundaries
- The diary is outside the API entirely. Beside every token the member reads: “Tokens and webhooks can never see your diary.”
- Free time only. Availability says when someone is free, never what fills the rest of their day or which calendar is busy.
- Other people’s details (a requester’s email or phone) need their own permission,
requests:contact. - No writes into a member’s day. Software asks with a request; the member accepts or declines in Daysli.
- No account, settings or export scope exists. Contacts, People, Inbox messages, Mail and Ring are not in the API.
- Answers are exact. Each answer is checked against its schema before it leaves; a field that was never meant to be sent is an error on our side, never a leak to you.