Blackboard Learn is automatable through its API

Blackboard Learn is automatable today through its REST API. The Learn REST introduction says the API can create, read, update, and delete users, courses, and enrollments, manage course content, and manage gradebook columns and grades. Authentication is OAuth 2.0. The page titled Basic Authentication with REST says the application key and secret are sent as HTTP Basic to POST /learn/api/public/v1/oauth2/token with grant_type=client_credentials. The JSON response contains access_token, token_type bearer, and expires_in 3600. Later calls send Authorization Bearer. The Learn instance must be registered with the developer portal, and a Learn administrator installs the application ID and chooses the user the integration acts as. Tokens are tied to one Learn site. Three-legged OAuth lets the application act as the signed-in user. That flow starts at /learn/api/public/v1/oauth2/authorizationcode and exchanges the code at the same token endpoint. The offline scope returns a refresh token. PKCE is documented from Learn 3700.4. The first steps page says three-legged OAuth applies to Learn 3200.7 in SaaS and, from Q4 2017, to self-hosted and managed-hosted clients. Developer signup is free. Deploying an integration can have a cost, and the product page describes a core license. Quotas and rate limits apply. The developer docs home lists Ally as its own API. No Blackboard Learn MCP server was established from the pages opened here. Connector catalogs were not opened. Computer-use viability is unassessed. The API scores 6 because the resource surface is broad and every call still depends on a developer-portal application plus a Learn administrator.

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