Web Scheduler (Legacy Embed) — Migrate to Web Widgets

This page covers the legacy Web Scheduler embed script. The current way to add OnePath to your site is Web Widgets — one loader script for the booking scheduler and chat.

Setting up OnePath for the first time?

Follow the Web Widgets guide — it is the current integration and takes one script tag. This page is only for sites still running the legacy embed script.

Am I on the legacy embed?

Search your site's HTML for onepath. You are on the legacy embed if you find script tags ending in onepath-embed.js or onepath-web-chat-embed.js:

<script src="https://cdn.onepath.ai/web-scheduler/onepath-embed.js" data-token="..."></script>
<script src="https://cdn.onepath.ai/web-scheduler/onepath-web-chat-embed.js" data-token="..."></script>

If your site loads https://cdn.onepath.ai/loader.js instead, you are already on Web Widgets — nothing to do.

The legacy scripts still work, but new capabilities (opening the scheduler from your own forms, booking events for analytics, context attributes) ship only to Web Widgets.

Migrate in one edit

Remove every legacy OnePath script tag and replace them with the single loader in your document head:

<!-- Remove these -->
<script src="https://cdn.onepath.ai/web-scheduler/onepath-embed.js" data-token="..." data-brand-color="#..."></script>
<script src="https://cdn.onepath.ai/web-scheduler/onepath-web-chat-embed.js" data-token="..."></script>

<!-- Add this instead, inside <head> -->
<script src="https://cdn.onepath.ai/loader.js"></script>

What changes:

No data-token. The loader recognizes your account from the domain the page is served on. The domain must be listed under Web Scheduler → Websites in OnePath — where to add it.
No data-brand-color / data-text-color. Colors and logo now come from your account settings, so they stay consistent everywhere without touching your site.
One script instead of two. The loader serves both the scheduler and chat — whichever is enabled on your account.

What stays the same:

Your trigger buttons keep working unchanged. data-onepath-web-scheduler-trigger and data-onepath-web-chat-trigger are the same attributes in Web Widgets — no markup changes needed.

Using an inline (self-hosted) embed?

The legacy data-self-hosted / data-target-container script attributes have no Web Widgets equivalent — inline embedding is now configured on your OnePath account. Contact OnePath before removing the legacy script so the switch is seamless.

What you gain

Open the scheduler from your own form, pre-filled with the visitor's details — Form-Trigger Integration
Attach the package or plan a visitor picked to their booking — context attributes
Wire bookings to analytics and post-booking redirects — Events