LTI 1.3 Integration: Canvas

In Canvas, select Admin>Developer Keys and click + Developer Key. Select the LTI Key option. 

You will need the following information to add a new developer key in Canvas:

  • Key Name: Apidapter LTI 1.3
  • Owner Email: Email of LMS admin
  • Redirect URI: (your adapter URL)
  • Configure: Manual Entry
  • Title: Apidapter 
  • Description: Tool description here.
  • Target Link URI: (your adapter URL)
  • Open ID Connect Initiation URL: (your adapter URL)
  • JWK Method: Select Public JWK URL and enter (your adapter URL with "/keyset" added at the end)

Key Settings: Nothing should be selected here.

LTI Advantage Services: Nothing selected here.

Additional Settings: This is where the client can add the custom parameters to the Custom Fields area under Additional Settings.


From the Placements drop-down select:

  • Course Navigation - Places the tool within the main course navigation.
  • Link Selection - Places the tool within a list of available course tools.

LTI 1.3 Tool Deployment

  1. Copy the Client ID created in the steps above.
  2. Navigate to Admin>Settings>Apps>View App Configurations>+ App.
  3. Select Configuration Type: By Client ID
  4. Paste the Client ID from the Developer Key step above and click Submit.
  5. Verify and install the Apidapter app by clicking Install.

Retrieve the Deployment ID

  1. On the View App Configurations page, locate your tool, click the gear icon, and click Deployment ID.
  2. Copy the Deployment ID. Add the Client ID and Deployment ID into your adapter's LTI 1.3 request handler.
  1. When in a Course, click the Modules link in the Course Navigation.
  2. In the Module where you’d like to add the link, click the + button.
  3. In the Add [Item Type] To: drop-down menu, select External Tool.
  4. Locate your external tool and review the following:
    • URL: This will pre-populate based on how the LTI External App was configured. 
    • Page Name: This will pre-populate based on the name of the LTI External App, but it can be edited.
    • Load in a new tab: We recommend checking this box to open the tool in a new tab.

Canvas Issuer

As the issuer, Instructure-hosted Canvas instances all use the following, regardless of the specific account domain(s) that the tool was launched from:

  1. (Production environment launches)
  2. (Beta environment launches)
  3. (Test environment launches)

Canvas Authentication Request

For cloud-hosted Canvas, regardless of the domain used by the client, the endpoint is always:

  1. (if launched from a production environment)
  2. (if launched from a beta environment)
  3. (if launched from a test environment)
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk