Schedule-X Cloud
Schedule-X Cloud is a hosted backend for applications that use the Schedule-X calendar UI. It stores users, calendars, and events and runs Google Calendar synchronization.
API base URL:
https://cloud.schedule-x.comWhat Runs Where
Section titled “What Runs Where”| Runtime | Code and credentials |
|---|---|
| Your backend | Uses ScheduleXServerClient. Stores the secret organization API token, maps your users to Cloud users, and issues short-lived frontend tokens. |
| Your frontend (browser) | Uses ScheduleXBrowserClient and the Schedule-X calendar UI. Receives only a short-lived frontend token for the signed-in user. |
| Schedule-X Cloud backend | Hosts the HTTP API, persists calendar data, enforces permissions, and runs Google Calendar synchronization. You call it through either SDK client; you do not deploy this code in your frontend. |
In these docs, backend means trusted server-side code in your application, while frontend means code shipped to the browser. The Schedule-X Cloud API is also a backend service, so we call it the Cloud backend when the distinction matters.
Integration Shape
Section titled “Integration Shape”- Create a workspace in the Cloud Console.
- Create an API key for an environment.
- Keep that
sx_org_...key on your backend and use it only withScheduleXServerClient. - From your backend, create or map Cloud users and calendars.
- From your backend, issue a short-lived frontend token for the signed-in app user.
- Send only that frontend token to your frontend.
- In the browser, use
ScheduleXBrowserClientto load Schedule-X config and write events.
- Quickstart gets a working integration running.
- Auth Flow explains the two token types.
- Core Workflows shows the basic SDK calls.
- Google Calendar Sync covers Google account connection and calendar import.
- TypeScript SDK covers the server client, browser client, and Schedule-X preset.
- API Reference lists endpoints, auth headers, and payloads.