Requesting preauthorization to connect with Badgr

Most Instructure-hosted Canvas instances are automatically authorized

If your institution's Canvas server is hosted by Instructure, most likely, you'll automatically be approved to connect to our Badgr servers in any location when you add the LTI.

Some Instructure-hosted Canvas instances may need to be manually authorized.

If, after adding the Badgr LTI to your course, sub-account or account, you see an error message like the one below, email us your Instructure-hosted Canvas server URL (e.g., myschool.instructure.com). 

 
If you see the message below, please provide the URL as it appears in the message.
Badgr_Server_preauthorization

Beta and test installations 


If you'd like to see how the badge-issuing process works before integrating with your production server, you can integrate Badgr with an Instructure-hosted Canvas beta or test installation. For more information, see Instructure's What is the Canvas release schedule for betaproduction and test environments?

 

Requesting to connect a self-hosted Canvas server

If your institution hosts its own server, connecting Badgr to the Canvas application is easy.

In order to connect Badgr to a self-hosted Canvas installation, we require your site to have an SSL certificate. Next, you'll need to create a developer key and then send us your ID, secret Key string and Canvas server URL. Badgr uses the developer key to sign OAuth 2.0 requests so that teachers can connect to their Badgr accounts and issue badges to students — and our application can be securely identified by your server.

Creating a developer key is a one-time set-up process, after which any instructor on your instance of Canvas can add Badgr as an LTI app to a course, or an administrator can add Badgr across a whole account or sub-account.

For more information, see Instructure's How do I add a developer key for an account?

  1. As an administrator, navigate to the managed account for which you would like to create a developer key
  2. In the left menu, select Developer keys
  3. Click the Add developer key button
  4. In the dropdown menu, select +API key.dev_key_api
  5. Create a new developer key for Badgr with these suggested settings (only the Redirect URI is essential)
    1. Key name: Badgr
      Owner email: <your email>
      Redirect URI (Legacy): https://api.badgr.io/  
      Redirect URI: https://api.badgr.io/   (<- optional)
      Icon URL: https://api.badgr.io/static/images/logo.png 
 
 

If you are connecting to a server outside the US (AU, EU, CA), please include the country code in the URI (e.g. https://api.eu.badgr.io/)  

If you see {“error”:“invalid_request”,“error_description”:“redirect_uri does not match client settings”}, please leave the Redirect URI field blank, but include the Legacy URI. Additionally, if you are still experiencing issues please try the following http://api.eu.badgr.io/badgebook/oauth2/return in the Legacy URI field.
 

authorization2

Sending your ID, key and URL

Be sure to select the entire field when copying the information.

  1. Once you've created a developer key for Badgr, select Details on the Developer keys page.
  2. Email us with your developer ID, secret key string and Canvas server URL. 
    1. The key string will be hidden by default until you mouse over it. 
    2. Canvas only displays about 20 characters of the key string, but it is 64 characters long for self-hosted instances (typically).
  3. Once we confirm your installation is connected to Badgr, you and other Canvas instructors will be free to add Badgr to courses.