LTI 1.3 places Raison inside Canvas courses and tells Raison which user, which course, and which role is launching the tool. Raison publishes its whole LTI configuration as a JSON file, so there are no endpoints, placements, or LTI Advantage toggles to fill in by hand.
Set up the API connection first. See Canvas setup: API connection (OAuth).
Official Canvas documentation: Configuring LTI Advantage tools.
Create an LTI developer key
In Canvas, go to Admin → Your Canvas account → Developer Keys, then + Developer Key → + LTI Key.
Field | Recommended value |
Key Name |
|
Owner Email |
The key name is only visible to Canvas administrators. The title learners see in the course menu comes from the configuration and can be edited later on the developer key.
Load the Raison LTI configuration
Set Method to Enter URL and paste this address into the JSON URL field:
https://services.raison.is/integration/lti/config/canvas.json
The same URL is available in Raison under Organization → Integrations → Canvas → Configure → LTI, as Canvas configuration URL.
Save the key, then switch it On in the State column of the Developer Keys list.
Copy the LTI Client ID into Raison
Copy the Client ID from the Details column and paste it into the Client ID field under Organization → Integrations → Canvas → Configure → LTI.
Install the Raison application in Canvas
Go to Admin → Your Canvas account → Settings → Apps.
Select + App.
Choose By Client ID as the configuration type.
Paste the LTI Client ID.
Select Submit, then Install.
Installing at account level generally makes Raison available to all courses in that account, subject to your Canvas configuration. You can also install per course from Course → Settings → Apps.
Retrieve the Deployment ID
Find Raison in the list of installed applications, open the gear icon, select Deployment ID, and copy the value into the Deployment ID field in Raison.
Complete the LTI settings in Raison
Enter your Canvas URL in the Canvas URL field first. Raison auto-fills the authorization, token, and JWKS URLs. The issuer defaults to https://canvas.instructure.com. Verify each value before you save.
Field | What to enter | Fixed or specific? |
Client ID | The Client ID of the LTI developer key | Specific to your Canvas instance |
Deployment ID | The Deployment ID generated when the app was installed | Specific to each deployment |
Issuer URL |
| Always the same for Instructure-hosted Canvas |
Authorization URL |
| Specific to your Canvas instance |
Token URL |
| Specific to your Canvas instance |
JWKS URL |
| Specific to your Canvas instance |
Replace [your-canvas-domain] with your actual Canvas domain. For an instance at https://canvas.example.edu, the authorization URL is https://canvas.example.edu/api/lti/authorize_redirect.
On the Issuer URL: all Instructure-hosted Canvas instances use https://canvas.instructure.com, regardless of the domain your institution uses. Some self-hosted or specially configured environments may differ. Check with your Canvas administrator if a launch fails.
Select Save LTI settings.
Test the LTI connection
Open a Canvas course and select Raison AI Assistant in the course navigation (the default tool title; Canvas administrators can rename it on the LTI developer key). Either the assistant opens, or you get a message saying no assistant is attached to this course. Both confirm the launch works.
What Canvas sends to Raison at launch
At every LTI launch, Canvas passes:
The learner's identity (name, email, user ID)
The course context (course ID, course name)
The user's role (instructor, student, admin)
This allows Raison to place the learner in the right course automatically and apply the correct permissions without any additional login.
LTI checklist
The LTI developer key is enabled in Canvas
The Raison JSON configuration URL was accepted
The application is installed in the Canvas account
Client ID and Deployment ID are saved in Raison
Issuer, authorization, token, and JWKS URLs are correct
Raison opens from inside a Canvas course
Related
Need help? Write to [email protected].