Can AI agents automate Canvas LMS?

Canvas LMS is automatable today through Instructure's REST API. Current docs live on the Instructure Developer Documentation Portal at developerdocs.instructure.com/services/canvas. The older canvas.instructure.com/doc/api/ page still serves the same contract and states that it redirects after 2026-07-01. All API access is HTTPS JSON against the institution's Canvas domain. Authentication is OAuth2 (RFC-6749): developer keys issue client ID and secret, the authorization code grant returns an access token and refresh token, and callers send Authorization Bearer. Tokens issued after October 2015 expire in one hour. Manual profile tokens are allowed only for the developer's own testing. GraphQL is at POST /api/graphql and can run any query or mutation the authenticated user may perform. The resource index includes accounts, courses, enrollments, assignments, submissions, quizzes, users, files, SIS imports, LTI registrations, and many other LMS objects. Institutions issue and enable developer keys; scoped keys restrict endpoints. Live Events deliver HTTPS webhooks or AWS SQS for analytics and are not the path for immediately consistent reads. SIS CSV imports load users, courses, and enrollments. Content export jobs produce Common Cartridge, QTI, or zip packages. LTI Advantage uses developer keys and a client_credentials JWT grant for Names and Roles and Assignment and Grade Services. Instructure publishes developerdocs.instructure.com/llms.txt. This record is Instructure Canvas LMS, not Canva. Nordic adoption was not assessed. Vendor documentation does not settle first-party MCP ownership. Third-party registry listings were not opened. No official general-purpose LMS SDK or CLI was established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path.

Best path today: api · Overall automatability: 8/10