Is there an npm package?

No. Every integration loads a CDN bundle from widgets.medos.one, which carries its own runtime, so there is no build step, no framework lock-in and no peer dependency to reconcile. The old medos-sdk npm package is deprecated.

Which frameworks does the SDK work with?

Anything that renders HTML. The docs have install guides for vanilla HTML, React, Next.js, Vue, Angular, Svelte, Gatsby, PHP and Laravel.

Is the publishable key safe in my page source?

Yes, that is what it is for. It is locked to your website’s domain and only lets a widget do what a patient could do in the booking flow. Backend work uses a separate, secret Developer API key.

Can I load only the widgets a page needs?

Yes. Each widget is its own bundle with its own global, so a page loads only what it uses, and single-page apps can load a bundle on demand.

Client SDK

Four patient-facing widgets, one script tag each.

Booking, the patient portal, enquiries and package sales, each a self-contained browser bundle from widgets.medos.one. No npm install, no build step, themed to the website you already have.

Read the SDK reference Talk to us about an integration

The SDKs

Booking SDK: window.MedosBooking · /v2/unified.js; The full appointment journey: practitioner, visit type, slot or queue token, OTP and payment. The widget reads each practitioner’s setup and shows scheduled slots or a live queue on its own.
Patient portal SDK: window.MedosPatientPortal · /v2/portal.js; Returning patients manage their own appointments, family members and session credits on your website.
Enquiry SDK: window.MedosEnquiry · /v2/enquiries.js; A contact form that files the enquiry against your workspace, so the follow-up call starts with context.
Package purchase SDK: window.MedosPackagePurchase · /v2/packages.js; Sell a multi-session package on its own page; sessions are drawn down visit by visit afterwards.

The whole install

Booking on your site in the time it takes to paste this.

<script src="https://widgets.medos.one/v2/unified.js"></script>
<div id="medos-booking"></div>
<script>
  MedosBooking.init({
    apiKey: "mk_your_publishable_key",
    mode: "inline", // or "modal" to open over the page
    containerId: "medos-booking",
    onSuccess: (data) => console.log("Booked", data),
  });
</script>

What every widget shares

One publishable key: The same mk_ key works across all four widgets. It is public by design and locked to your website’s domain.
Your brand: Theme, primary and secondary colours, border radius, font family and size are shared options on every widget.
Inline or modal: Mount into a container on the page, or open over it from your own button.
Callbacks: onSuccess and onError tell your page what happened, for your own confirmation screen or analytics.

Install guides cover Vanilla HTML, React, Next.js, Vue, Angular, Svelte, Gatsby, PHP, Laravel.

What the widgets connect to

Straight answers

The SDK, answered.

: No. Every integration loads a CDN bundle from widgets.medos.one, which carries its own runtime, so there is no build step, no framework lock-in and no peer dependency to reconcile. The old medos-sdk npm package is deprecated.
: Anything that renders HTML. The docs have install guides for vanilla HTML, React, Next.js, Vue, Angular, Svelte, Gatsby, PHP and Laravel.
: Yes, that is what it is for. It is locked to your website’s domain and only lets a widget do what a patient could do in the booking flow. Backend work uses a separate, secret Developer API key.
: Yes. Each widget is its own bundle with its own global, so a page loads only what it uses, and single-page apps can load a bundle on demand.

Client SDK

Four patient-facing widgets, one script tag each.

The SDKs

The whole install

Booking on your site in the time it takes to paste this.

What every widget shares

What the widgets connect to

Straight answers

Product

Solutions

Resources

Company