LMS API Standards

Each of our clients has a unique business model that has made them successful. While LatitudeLearning provides many options to automate, customize, and integrate our platform into your training processes, some clients choose to launch a custom LMS interface. Those interested in designing, developing, and maintaining their own LMS experience can use our standard application program interface (API) to do so. 

Technical Considerations

All system data that is submitted, retrieved, and otherwise maintained through a custom user interface will come from API (web service) calls to LatitudeLearning.

  • The web service must be RESTful (https://www.tutorialspoint.com/restful/). REST stands for Representational State Transfer, which is an architectural style for networked hypermedia applications; it is primarily used to build Web services that are lightweight, maintainable, and scalable. 
  • Each API addresses authentication in the LMS. That is, each API must be accessible only to someone that has authenticated in the LMS. This can only be done in the API layer. 
  • Each API considers user authorization and security scoping. That is, each API must take into account who the authenticated user is, and what access they should be permitted in the system. Latitude must be prepared to provide several “scoping” utility methods to choose from as templates for addressing authorization. This also can only be done in the API layer. 
  • Important for LMS processing, the API needs to call same services in the business layer as are called by the LatitudeLearning interface. This will ensure the API is calling the right services for processing. 
  • Authenticated User ID must be recorded in LMS Audit Tables, as applicable. (i.e. User, Organization, etc.) LMS should automatically get and post that data from authenticated User Context. 
  • LMS information will be returned in a JSON object via the web service.

Contact our ClientCare team HERE to learn more.