MyLabs Plus products leverage LearningStudio for course and user management. The LearningStudio APIs allow you to build a more integrated learning environment for your students. They were developed to allow our clients to more seamlessly integrate their SIS systems and LearningStudio.
At a minimum, you can use APIs to sync users and automate course deployment and enrollment, simplifying MyLabs administration.
LearningStudio was one of Pearson's largest Learning Management Systems (LMS). It is a fully-hosted Software as a Service platform, offering scalability and deep analytics, a variety of learning tools, and a robust API suite for extending the platform in new and imaginative ways. As a multitenant, Software-as-a-Service offering, Pearson hosts the platform on our servers on your behalf. With few exceptions, all clients are on the same version of LearningStudio all the time.
MyLabs Plus used LearningStudio as the container for course and user management and accessing the MyLabs content and activities.
The platform offers a number of integration options, including SOAP-based APIs for creating courses and users and inbound Single Sign On from your portal or system into LearningStudio or a specific course. All of these features are documented in our developer community, the Pearson Developers Network.
The Pearson Developers Network is the source for all documentation related to the LearningStudio API ecosystem. This guide is a summary of that information tailored for MyLabs Plus clients, with links to relevant pages on the PDN portal. When you have a general question about the APIs, their capability or behavior, or asking about how to do something with them, please use the Developer Community.
You can also email email@example.com to reach the Support Engineering team. We are happy to help with particularly tricky use cases or instances where information shouldn’t be posted to the open community.
Every client is an isolated tenant on the LearningStudio platform. We call each tenant a campus and each campus’ data is only accessible using a unique set of API keys. A campus can have any number of nodes, which are logical groupings of users and courses.
Terms are time-based containers for courses, setting the start and end dates for courses. Courses have a start and end date, and so there may be many copies of the same course across multiple terms.
Each node is identified by a client sort string which looks like:
strata.humanities. When integrating your SIS with LearningStudio, you will need the client sort string where a course is to be created.
Courses are identified by an integer Course ID. They can also be identified by any number of Call Numbers, which is the client’s catalog identifiers for the course. You use these identifiers in Course APIs.
Users are identified by an integer User ID. They can also be identified by a single Login ID, which is the client’s identifier for them and/or the method by which the user signs into LearningStudio. You use these identifiers in Course APIs.
LearningStudio can integrate with your SIS to drastically simplify or automate term and course creation and user enrollment. There are two approaches.
Batch files are comma-separated value (CSV) files or XML files that contain all the changes to make to LearningStudio; these files are uploaded to a secure FTP server, where they are pitched up and processed. Each new course or user enrollment is a line in the CSV file (or an element in the XML file). They are particularly helpful when making mass changes (e.g., at term start), or infrequent changes; this approach is also quite flexible regardless of what SIS you use. The downsides are that it can take up to 24 hours to process the files, you cannot change user login IDs, and you cannot create terms.
The SIS APIs are SOAP-based services that allow you to more deeply connect LearningStudio with your SIS. These APIs are nearly synchronous, so the changes are reflected quickly. When you need to keep LearningStudio and your SIS more exactly synchronized, or if you need to make more frequent, individual changes, use these APIs. The downside is that SOAP is more difficult to use (though we are happy to answer questions) and these require custom programming, but generally the SIS APIs create a better integration.
When integrating LearningStudio into your learning ecosystem, you have two choices for how your users will access their courses. The default option is allowing them to sign in directly to LearningStudio - in which case you need to keep their passwords up to date through SIS Integrations (or allow them to self-manage their password). The other option is to manage usernames and passwords yourself, and using Single Sign On to seamlessly send them to their courses.
As part of the SSO transfer, you can send the student to the LearningStudio dashboard (Personal Student Home) or directly to a particular course.