Migration & Changelog

Migrating from the legacy widgets

Earlier versions of the SDK shipped three separate CDN widgets:

MedosAppointment — scheduled appointments
MedosPackagePurchase — package purchase
MedosQMS — queue management

The Unified Booking Widget (MedosBooking) supersedes all three. It handles every flow in one bundle and auto-detects which UI to show per doctor.

What changed

Before	After
`window.MedosAppointment.init`	`window.MedosBooking.init`
`window.MedosPackagePurchase.init`	`window.MedosBooking.init` (auto-detected via session packs)
`window.MedosQMS.init`	`window.MedosBooking.init` (auto-detected for QMS doctors)
Three CDN bundles	One CDN bundle: `https://widgets.medos.one/v2/unified.js`
Per-widget config surface	Single config object with the same option names

What stayed the same

API keys are unchanged.
Callback signatures (onSuccess, onError, onClose) are unchanged.
Theme system is unchanged (default, modern, custom themes).
containerId, mode, baseUrl, medosDoctorId all mean the same thing.

Migration steps

Replace the script src:

- <script src="https://widgets.medos.one/v1/appointments.js"></script>
- <script src="https://widgets.medos.one/v1/qms.js"></script>
+ <script src="https://widgets.medos.one/v2/unified.js"></script>

Rename the global:

- MedosAppointment.init({ ... });
- MedosQMS.init({ ... });
+ MedosBooking.init({ ... });

Config options carry over 1:1. No renaming needed.

Handle mixed success payloads. If you were only receiving appointmentId before and you're now serving QMS doctors, your onSuccess might receive a QueueToken instead. See onSuccess for the two shapes.

Backwards compatibility

The legacy v1 bundles still ship for a transition period. New sites should use unified.js directly.

Versioning

The widget follows semantic versioning:

Patch releases (x.y.Z) — bug fixes only, no API changes.
Minor releases (x.Y.z) — additive: new options, new callback fields, new supported system types. Existing calls keep working.
Major releases (X.y.z) — breaking changes to the public API. Announced ahead of time with migration notes.

The current major line is v2. The CDN URL includes the major version so you can pin explicitly if needed.

Changelog

Release notes will be published at the same URL your team distributes release announcements. Ask the platform team for the current release notes if you need them today.