Get Started
Test vs live mode
How to develop against a sandbox before switching to production.
Medos uses environment-scoped API keys to separate test bookings from real ones. Test keys hit a sandbox that doesn't create real appointments or notify real patients.
Two environments
| Environment | Key prefix | What happens |
|---|---|---|
| Test | mk_test_ | Bookings are simulated. No SMS or emails are sent to patients. |
| Live | mk_ | Bookings are real. Patients receive SMS and email. |
Key format is being finalized
The exact test-key prefix and dashboard toggle are still being confirmed with the platform team. Treat the table above as the intended shape; we'll lock the specifics before this page ships to production.
Point the widget at a custom API base URL
For local development or staging, use the baseUrl option to point the
widget at a non-production API:
MedosBooking.init({
apiKey: "mk_test_...",
baseUrl: "https://staging-api.medos.one/v1",
mode: "modal",
});If baseUrl isn't set, the widget uses the default API base URL for the
build it's running against.
Switching to live
Before flipping to a live key:
- Test the full flow end-to-end with a real doctor in your workspace.
- Verify the confirmation email/SMS templates in your dashboard.
- Make sure your dashboard has the correct workspace theme if you're relying on auto-theme detection.
- Restrict the live key to your production domain in the dashboard.