LTI integration for e-learning: let your users start immediately

Single Sign-On (SSO) via the Learning Tools Interoperability (LTI) standard enables users who enrolled for an E-Learning course to start immediately. When LTI is enabled, neither provider nor user have to create an account in order to start the E-Learning course. Instead, the credentials of the user will directly be sent to your LMS (Learning Management System) or CMS (Content Management System) via the LTI protocol. This increases usability for the user and takes away manual labour for providers.  

How does it work?

When Single Sign-On is activated and your "bookings" service is enabled on Springest, an "Enrol now" button is displayed on each product page. This button will direct users to the enrolment form. After enrolment, the user can directly click on a  "Start now" button. This will send the user to the requested course in the provider's online environment. 

What does it look like?

On / / and Go sites
On the left you can see an example of what this looks like on a product page on, before the user has enrolled. On the right you can see what it looks like after the user has enrolled.  

How can I activate LTI?

Does your system support LTI? Then you can enable Single Sign-On via LTI for all of your E-Learning products. At the moment this feature can only be enabled by Springest. So if you want to use LTI, or should you have any questions, please contact our helpdesk. We are more than happy to help you enable LTI on all of your products. 

Technical implementation and guidelines

We have set up our SSO via LTI according to the documentation of IMS Global, the organisation behind LTI:


  • Springest is on LTI v1.1. Newer versions are backwards-compatible, so if you are using a newer version it does not negatively impact the SSO.
  • Springest only supports a one-way connection: we send data to the provider's system. We cannot (yet) receive back information (such as progress).

Our system is flexible. We support SSO via LTI in multiple ways: 

1. Your system works with one Launch URL for all of your products

In this case you have to provide us with:

  • The Launch URL
  • Consumer Key and Consumer Secret Key, with two options:
    • You deliver one Key and Secret Key that applies to all of your products
    • You deliver a Key and Secret Key per product
  • Per product: one custom parameter that serves as an unique id for the product

2. Your system works with a separate Launch URL per product

In this case you have to provide us with:

  • The Launch URL per product
  • Consumer Key and Consumer Secret Key, with two options: 
    • You deliver one Key and Secret Key that applies to all of your products
    • You deliver a Key and Secret Key per product

Note: are your products published on multiple Springest sites? Then it is possible –and advised– to have separate Consumer and Secret Keys per site.