Imperial Canvas LTI 1.3 / OIDC Platform Endpoints

Imperial's Canvas tenancy publishes the two documents an LTI 1.3 tool integrator actually needs, unauthenticated, on Imperial's own hostname: an LTI platform JWKS at /api/lti/security/jwks (200, 1,408 bytes of RSA public keys used to verify launch id_tokens), and an OIDC discovery document at /.well-known/openid-configuration (200, issuer https://canvas.imperial.ac.uk, RS256, authorization_code). The Canvas REST API itself is present but gated — /api/v1/accounts/self answers 401 "user authorisation required". No SCIM surface is exposed. This is the closest thing Imperial has to a documented, standards-conformant integration point, and it is Instructure's work.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/canvas-lti-platform"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: imperial-college-london:canvas-lti-platform
name: Imperial Canvas LTI 1.3 / OIDC Platform Endpoints
x-operator: tenant
x-operator-evidence: canvas.imperial.ac.uk is a CNAME to imperialcollegelondon-vanity.instructure.com.
  The platform is Instructure Canvas. The keys, the tenancy and the launches are Imperial's; the LTI implementation
  is Instructure's.
description: 'Imperial''s Canvas tenancy publishes the two documents an LTI 1.3 tool integrator actually
  needs, unauthenticated, on Imperial''s own hostname: an LTI platform JWKS at /api/lti/security/jwks
  (200, 1,408 bytes of RSA public keys used to verify launch id_tokens), and an OIDC discovery document
  at /.well-known/openid-configuration (200, issuer https://canvas.imperial.ac.uk, RS256, authorization_code).
  The Canvas REST API itself is present but gated — /api/v1/accounts/self answers 401 "user authorisation
  required". No SCIM surface is exposed. This is the closest thing Imperial has to a documented, standards-conformant
  integration point, and it is Instructure''s work.'
humanURL: https://canvas.imperial.ac.uk/
baseURL: https://canvas.imperial.ac.uk
tags:
- Learning Management
- LTI
- OIDC
- Education Technology
properties:
- type: x-jwks
  url: https://canvas.imperial.ac.uk/api/lti/security/jwks
- type: x-openid-configuration
  url: https://canvas.imperial.ac.uk/.well-known/openid-configuration
- type: Conformance
  url: conformance/imperial-college-london-education-standards.yml