Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

  1. Home
  2. Knowledge Base
  3. Learning Management Systems
  4. Installing in the LMS
  5. Creating Canvas Developer Credentials for the Hypothesis LMS App – LTI 1.1 (Worldwide)
  1. Home
  2. Knowledge Base
  3. Learning Management Systems
  4. Canvas
  5. Creating Canvas Developer Credentials for the Hypothesis LMS App – LTI 1.1 (Worldwide)

Creating Canvas Developer Credentials for the Hypothesis LMS App – LTI 1.1 (Worldwide)

This legacy guide is for installing the LTI 1.1 version of Hypothesis and is no longer current. For instructions on installing the LTI 1.3 / Advantage version of the Hypothesis LMS app please see this page.

This guide is for schools without specific data residency requirements. For compliance with Canadian data residency requirements please see the Canadian version of this guide.

To enable advanced Hypothesis integration with Canvas, a Canvas administrator will need to generate a Canvas API Developer Key before Hypothesis is installed.

This key will be tied to the Hypothesis LTI tool, and enables the following deeper integrations with Canvas:

  • Access to Canvas Files for documents
  • Integration with Canvas Groups
  • Integration with Canvas Sections

For more detail, please see our article on the Canvas API endpoints used by the Hypothesis LMS app.

Note that deleting the API Developer Key and/or creating a new API Developer Key for Hypothesis will require installing a new instance of Hypothesis in Canvas.

1. Create a new Canvas Developer Key for Hypothesis

Navigate to Admin > Developer Keys, click on the +Developer Key button, and select the +API Key option.

Add Canvas Developer Key page

2. Fill out the Key Settings form

  • Key Name:
    • Hypothesis
  • Owner Email:
    • Enter an appropriate email address
  • Redirect URIs (make sure there are no extra spaces or characters copied and pasted here):
    • https://lms.hypothes.is/canvas_oauth_callback
      https://lms.hypothes.is/module_item_launch_oauth_callback
  • Redirect URI (Legacy):
    • leave blank
  • Vendor Code (LTI 2):
    • leave blank
  • Icon URL:
    • https://d242fdlp0qlcia.cloudfront.net/uploads/brand/HypothesisCanvasIcon.png

If your institution enforces scopes on the Developer Keys, see below for the list of API endpoints to enable.

Click the Save Key button in the lower right corner to finish.

3. Turn the Key on.

Canvas does not turn on Developer credentials by default. Turn on your Developer Key before leaving this page.

Location of

The ID (shown in the Details column) and Key (shown in a pop-up once you click the Show Key button) will correspond to the Canvas Developer ID and Canvas Developer Key fields in our form to generate Hypothesis credentials:

Locations of Developer ID and Key

Canvas API endpoints required by Hypothesis

If your institution enforces scopes on Developer Keys, you will need to enable the following API endpoints for Hypothesis’ Developer Key (organized by category):

  • Courses
    • url:GET|/api/v1/courses/:id (3rd endpoint from top)
    • url:GET|/api/v1/courses/:course_id/users/:id (13th endpoint from top)
  • Files
    • url:GET|/api/v1/courses/:course_id/files (1st endpoint)
    • url:GET|/api/v1/files/:id/public_url (26th endpoint from top)
  • Group Categories
    • url:GET|/api/v1/courses/:course_id/group_categories (5th endpoint from top)
    • url:GET|/api/v1/group_categories/:group_category_id/groups (9th endpoint from top)
  • Groups
    • url:GET|/api/v1/courses/:course_id/groups (10th endpoint from top)
  • Sections
    • url:GET|/api/v1/courses/:course_id/sections (1st endpoint)
  • Pages
    • url:GET|/api/v1/courses/:course_id/pages  (6th endpoint)
    • url:GET|/api/v1/courses/:course_id/pages/:url_or_id  (8th endpoint)

Additionally, you must enable the use of Include ParametersLocation of Allow Include Parameters checkbox

Was this article helpful?

Related Articles