Connection to ExorLive

Simplest web-to-web method

There are several ways to connect a partners web based application to ExorLive. The methods described here shows the basics of a simple case.

Use case

The typical use case is: As a user of web program X, I want to press a button, e.g. named "Exercise Programs" to create exercise programs to my client / patient / contact. When I press the button ExorLive opens and the data about my contact is transferred from program X to ExorLive.


A demo of this is found here: Demo

The source code of this demo is found here: Download samplecode.
This code is written in Visual Studio as a .NET / C# web project, but the principles used here should apply to other environments as well.

You may test this demo with your own ExorLive account. Press the "Exercise Programs" button and follow the instructions.

Further reading

When you got the basics going as described here, you may expand the integration between your application and ExorLive.

Check out these links:


This demo uses the ExorLive web-to-web framework. If you have special interest in this, you might want to know that under the hood here we use a framework called easyXDM which allows for cross domain communication between one webpage in one tab and another webpage in another tab.

Steps to get going with your own ExorLive client connection.

  1. Study the samplecode of the demo.
  2. The code has many comments and it should be enough for you to be able to do the same in your own application. The hardest part for many is the OAuth 2.0 flow, i.e. some knowledge about OAuth 2.0 is recommended for best results.
    The basics are found in our authorization section.
    Further details about ExorLive's OAuth 2.0 implementation is found here:
  3. The samplecode is a working demo, except for some fill-in parts for the authorization details that identifies your application.
  4. Contact ExorLive API support at and we will issue the authorization details tailored to your needs.
    You will get:
    • Application key/client id: xxxxxxxxxxxxxx
    • Application secret/client secret: xxxxxxxxxxxxxx
    • This key/secret will be valid for requests from the domain name (callback URL) you provided.
  5. Contact us at if you have any questions.