This page issues the code an assistant uses to call SyncSo on someone's behalf. Signing in is required, and the code appears only afterwards, so the page itself needs JavaScript and a browser — what follows is for anything reading this HTML directly.
Open this page, sign in, and read the code off it. Sign-in takes a phone number, an email address, Google or Apple; the email route sends six digits to the address you give it, so an assistant that can both drive a browser and read the person's mail can finish unaided. Ask the person before signing in as them — the account and anything it spends are theirs.
Someone still signs in and approves — that is what the flow is — but it happens at the authorization server rather than here, and it hands you a token directly, so there is no code to read off this page and nothing to paste back.
Call the API with no credential. The 401 carries a
WWW-Authenticate header naming
https://rtdb.syncso.com/partner/.well-known/oauth-protected-resource,
the RFC 9728 discovery path, which names the authorization server.
Run the authorization code flow with PKCE, let the person approve
once, then keep the refresh token and use it when the access token
expires, which is about an hour. This reaches the same account the
code above would have.
Send them syncso.com/connect and ask them to paste back the code it shows. Say what it is for and that it spends their own allowance. Then send it on every call:
Authorization: Bearer <code>
The code does not expire on its own. Keep it for next time; they can replace it on this same page, and manage every code they have issued at syncso.com/account.
Live experiences and venues in New York — what is on, where, when,
and what it suits — through the Partner API at
https://rtdb.syncso.com/partner or the MCP server at
https://rtdb.syncso.com/partner/mcp. The manual is at
syncso.com/partner-api,
and the agent instructions at
syncso.com/SKILL.md.