2025-06-18). You do not need to understand any of it to connect — this page is for people who want to know what is happening, or who are debugging.
What your AI client does
Nothing needs configuring because the server publishes its own metadata:
The client discovers those, registers itself, and runs a normal authorization-code flow with PKCE. That is why the only thing you paste in is the server URL.
Where the tokens live
Your Daysync credentials never reach your AI client.
Why it asks you to sign in every time
Connecting always forces a fresh sign-in, even if your browser already has a Daysync session. This is deliberate. The sign-in used for connecting is a separate session from app.daysync.com — different domain, no shared sign-on. Reusing whatever session happened to exist meant a connection could silently bind to an account you were not expecting, and then stay on it for weeks. Forcing the sign-in makes the bound account explicit at the moment you choose it. If you have several Daysync accounts, this is the moment to pick the right one. The consent screen also has a Switch account link.What the consent screen controls
The scopes you approve decide which tools your client can see. Approve only Tours · Read and you get the tour reading tools and nothing else. It is worth being precise about what consent is and is not:- Consent decides tool visibility.
- The partner credential’s scopes and your own Daysync role decide what actually succeeds.
403 INSUFFICIENT_SCOPE. And consenting to a write scope does not let you edit a tour you are only a viewer on.
The scope list on the consent screen is generated from the application’s real grant, so it should never offer you something that could not work.
Sessions and expiry
In normal use a connection lasts until you revoke it. If refresh fails, your client will prompt you to sign in again — that is the expected recovery path, not an error.
Checking and ending a connection
Two tools are always available, on any connection:
From the Daysync side, Settings → Integrations in the web app lists and revokes the connections belonging to your account.
Settings → Integrations only shows connections bound to your account. If a connection was bound to a different account it will not appear there — use the in-client
disconnect tool instead, then reconnect with the right account.See also: Scopes & Permissions for the full scope list, and Troubleshooting.