Everything you need to set up and start integrating with the VSee Clinic API.
VSee provides two separate environments. Each has its own domain, credentials, and data. Tokens from one environment will not work in the other.
To start building with the VSee Clinic API, you'll need a developer account. This gives you a staging clinic with API credentials to develop and test your integration.
Enter your API credentials below. They'll be saved in your browser and auto-populated across all use cases and the Try It feature, so you don't have to re-enter them for every request.
Sign up for a developer account to get a staging clinic with API access. See the sign up instructions for a detailed walkthrough.
You'll be assigned a staging clinic at yourcode.vseepreview.com.
Get your Account Code, API Key/Secret (for SSO), and Clinic Admin API Token from the staging admin dashboard.
Develop your integration against the staging API. All test data stays in the staging environment.
When your integration is tested and ready, request production credentials for your live clinic.
Here's a simple test to verify your credentials. This calls the Settings API, which only requires an Account Code:
curl -X GET https://api.vseepreview.com/api_v3/settings \ -H "X-AccountCode: YOUR_ACCOUNT_CODE"
If you get a JSON response with clinic settings, your Account Code is valid and you're connected to the right environment.
All 16 APIs are published as OpenAPI 3.0 specifications. Browse the full list and download any spec as raw JSON — ready to import into Postman, Swagger, or AI tools.
Browse OpenAPI SpecsIf you're building a web application, all API calls must be routed through your backend server. Your server-side code makes the API call, then returns the result to your frontend.
This usually means you're using the wrong token type for this endpoint. For admin operations (creating rooms, managing webhooks, etc.), you need the Clinic Admin API Token from the dashboard — not a user session token from login/SSO.
Your token may be expired, invalid, or from the wrong environment. Check that: (1) your token hasn't expired, (2) you're using staging tokens with the staging URL and production tokens with the production URL, and (3) your Account Code matches the environment.
The VSee API does not support CORS. You must route all API calls through your backend server. Direct browser-to-API calls will always fail with a CORS error.
vseepreview.com is the staging (test) environment and vsee.me is production (live). They're completely separate — different data, different credentials. Always develop and test in staging first.
Your clinic has a Clinic Admin API Token (for server-side admin operations) and user session tokens (returned when users log in). They serve different purposes and have different permissions. See the Authentication Guide for details.