Migrating from 1.0.0
In version 3.0.0 there are a number of changes to the API schema. In order to help make a smooth transition we've included callouts with information about changes to each endpoint in our reference API.
In each endpoint, if no concepts have changed to the endpoint itself (i.e. GET /appointments
which returns all appointments and does the same in version 3.0.0), you will find a link to the corresponding endpoint in version 1.0.0. Any major changes to the function of an endpoint will be boldly stated in a callout:
I Have News!
These callouts will tell you any major updates that have been made to the endpoint you are working with.
OnSched.js
Migrating OnSched.js has been made super easy! All you'll need to do to get started is swap your version number in the script
tag of your HTML. Once you've updated the version number, along with a couple minor property name changes, all of your booking flows will work seamlessly as no logic has changed to the usage of each Element.
For a detailed list of property name changes and updates please see Migrating from OnSched.js 1.0.0.
Full API Integration
Migrating to new versions can be a hassle, and we understand. To assist you, in addition to major updates on particular endpoints we're also offering white-glove support for any existing users who are excited to make the switch but are in need of a helping hand.
Click here to view the updated API Endpoints
Migrate Existing Data
All of your data from existing OnSched Companies in version 1.0.0 (i.e. Locations, Services, Resources, Customers, Appointments, etc.) may be copied to your version 3.0.0 profile by the OnSched team on request.
Once you are prepared to copy all data from version 1.0.0 (Sandbox or Production), notify our team with a request for data migration to the new version. Be sure to include the ID of the Company in version 1.0.0 that you wish to migrate, all assets from the Company provided will be copied to your profile on the new version.
Updated 8 days ago