Submit a request
Submit a request

Learnosity API Versioning

This article provides a general overview on how we implement versioning for our APIs.

Simplified Versioning

Instead of calling each API’s specific version, you call a single version, and we manage the complexity of serving up the correct version.

For example, rather than calling a discrete version number for Items APIAuthor API, and Reports API respectively -- you can simply specify v2022.1.LTS for all of them, and know the versions will all work together in perfect harmony.

Note: this pattern has been in place since the 6th of June, 2018, and is the supported versioning method.

For example:

Description Example
Template for API request URL 
- YYYY: four-digit year of release 
- X: incremental number identifying release in year 
- LTS: Moniker flagging long term support 
Note: Data API doesn't have a question mark (?) in the URL
Lock to 2022.1 Long Term Supported version of APIs
Track the latest release available of the API Items API Release Logs 
Author API Release Logs 
Reports API Release Logs 
Data API Release Logs

For further information and frequently asked questions, you can read our Easier Versioning for Learnosity APIs Blog Article.

Learnosity API Versioning (no longer supported)

Note: The information below is historical and hasn't been supported since June 2018.

To provide information that might be helpful when upgrading to a current Long Term Support release, the formats of legacy versioning syntax are provided below. These formats are no longer supported and will automatically be mapped to a current version of each API, described below. To maintain control over which versions you deliver, and allow testing before deployment, use the Long Term Release format above.

When looking at any occurrences of the following in your legacy codebase, the following will be true. Providing no version: https://<api_name>, or specifying a major version only: https://<api_name>, will deliver the dev-only developer version of the API. This has the same effect as specifying: https://<api_name> This can be useful for testing new features in a development environment only. However, we strongly recommend that you not use this format in production.

Legacy semantic versioning syntax also allowed you to specify a major.minor.patch version: https://<api_name> . This meant that version 1.0.3 of the API would be available at https://<api_name> As of July 8, 2020, this format will remap to the most-recent LTS release (see above).

The following table summarizes the previously available formats and their current outcome:

URL Description
https://<api_name> Development release available of the API. Dev-only.
https://<api_name> Development release available of the API. Dev-only.
https://<api_name> Most recent LTS release.
https://<api_name> Most recent LTS release.



Was this article helpful?
2 out of 2 found this helpful

Did you arrive here by accident? If so, learn more about Learnosity by clicking here.