Integration Flows

Where the API reference describes endpoints one at a time, these walkthroughs show how they fit together into something a user can actually click.

Each flow is explicit about which side does what. LTIAAS handles the LTI® protocol — handshakes, signing, verification, token issuing. Your LMS handles what only it knows: who the user is, which course they are in, what role they hold, and where their grades belong.

Start with the core launch. Deep linking builds directly on it, and the service requests only become relevant once a tool wants to read a roster or write a grade.

1. 1

   Core launch

   required

   Take a user from clicking an activity in your LMS to landing inside a third-party tool, signed in and in the right course.

   Walk through →
2. 2

   Deep linking

   optional

   Let a teacher browse a tool's content and pick what to add to a course, then store their selection.

   Walk through →
3. 3

   Handling service requests

   optional

   Answer the roster reads and grade writes that tools make after a launch, through your Service URL.

   Walk through →

Before You Start

Both flows assume you have configured your account and registered at least one tool. If you have not read how a launch works yet, read that first — the code below will make much more sense.