Brightspace includes all the APIs and tools that developers use to create valuable, integrated solutions for their customers. If you are new to integrating with D2L’s products, then you can use the documentation on this site to understand the state-of-the-world for extensibility at D2L.
Community Resources. Developers have access to the Developer Community of Practice that houses a set of resources including support forums, a developer blog, code samples, and the available developer support paths.
Known Issues/Fixed Issues List. The known issues and fixed issues lists for the developer platform are available in the Brightspace Community’s Documentation section. For known issues, you can find release specific information within the Cumulative Known Issues List document and for the fixed issues, within the Release Notes document.
All our documentation is open and we are working to provide clear tools and programs. We host all our available open software in our Brightspace repository on GitHub.
Technology features¶
Web 2.0 integrated and decoupled. We’ve based our architecture upon the practices of Web 2.0 and cloud services that permit richly integrated apps, easy configuration, and operational independence. All access to our system is supported through HTTP and HTTPS calls.
Oauth 2.0. Our support for OAuth 2 Authorization Code Grant workflows ensures that we can transparently support all customer authentication scenarios involving your applications. Also, by ensuring that all API routes into an LMS occur within the acting context of a particular user login, service administrators can be confident that activating your application is a safe and constrained step to take.
REST/JSON standards. As a result of using RESTful APIs and JSON data structures, we provide a broad and well-supported technology base for our platform. You will find many off-the-shelf tools you can use to help simplify your work. Additionally, we provide open-source library wrappers for a number of languages with an emphasis on prioritizing the more sophisticated authentication steps of your application’s interaction with an LMS.
Extensibility Areas. Our continually expanding suite of APIs provide access to a variety of technical functionality:
Area |
Notes |
|---|---|
Org and structural |
Retrieve and update organizational structure, course lists, user information, and more |
Content |
View and create content components and resources for a course |
Assignments and grades |
Facilitate assignment and assessment-related features |
Social |
Access to ePortfolio Collections, Artifacts, and activities of electronic portfolios |
Current release changes¶
Our Brightspace ILP in continuous delivery provides these new features and changes for the October 2026 release:
Learning Environment. Version 20.26.10 of the Learning Environment includes these changes:
We have added the SendUserExternalIds property for the
CreateDeploymentDataJSON structure used to create and update LTI deployments.As of LE API v1.100, we have added JSON structures and actions to let you
create,update, andretrievequiz questions.As of LE API v1.100, we have added actions and structures to let you retrieve and update rubric assessments for quiz questions, and to manage assessment rubric associations for different learning activities.
We have added JSON structures and actions to let you manage achievement scales for outcomes.
Learning Platform. Version 20.26.10 of the Learning Platform includes these changes:
We have added support to enrollments actions and structures to allow you to foward an enrollment from a specified source course to that course’s current offering.
As of API v1.64 and following, we’ve adjusted the action to
retrieve release conditions on a targetin an org unit so the calling user needs only the “View Release Conditions (API Only)” permission without requiring other permissions.We have added an action to
retrieve groups in which the calling user is enrolled.Group enrollment responses now include the user’s first name, last name, and username when the caller has the corresponding user information privacy permissions. See the action to
retrieve a group's enrollmentsfor more information.We have added an action to retrieve groups in an org unit that the user
can self-enroll into.We have extended the actions to
enroll intoandunenroll froma group, so that if the calling user has permission to “See Groups” but not to “Manage Groups and Sections”, and if the groups are configured for self-enrollment, then the user can self-enroll and self-unenroll themselves, following the rules for self-enrollment.
Previous changes. You can find details about previous platform releases on the history topic page.
API deprecation and obsolescence¶
With this release, the versions of our product component API contracts introduced with the following specific product components become (or remain) deprecated. While you can still call the routes in these contracts on the Learning Suites that have historically supported them, you should plan to migrate to the new API contracts available on your back-end service with due priority.
Code |
Oldest fully supported API contract |
Deprecated API contracts or services |
Obsolete API contracts or services |
|
|---|---|---|---|---|
Learning Platform |
lp |
1.49 |
1.46 to 1.48 |
1.45 and older |
Learning Environment |
le |
1.82 |
1.75 to 1.81 |
1.74 and older |
Learning Repository |
lr |
1.3 |
1.2 and older |
|
ePortfolio |
ep |
2.5 |
2.4 and older |
|
Awards Service |
bas |
1.4 |
1.3 |
1.2 and older |
Brightspace For Parents |
bfp |
1.0 |
Warning
API deprecation and obsolescence. We are serving notice that as of the Brightpace 20.27.1 release (projected for January 2027), the API contracts introduced with Learning Suites v20.25 will be deprecated and the API contracts introduced with the Learning Suite v20.24 (and earlier) will become obsolete.
Deprecation of legacy authentication workflow. As of Brightspace 20.23.1 release (January 2023) we have deprecated support for the legacy ID-Key authentication system. We encourage clients using this legacy authentication system to move to using OAuth 2 with due priority.
Versions and migration¶
All API routes to an LMS component are versioned, and include a version negotiation process. This process allows your applications to gracefully adapt to the product components that a customer has active. Additionally, it lets D2L maintain overlapping API versions in a particular product installation, giving your application’s development a way to transition to new features along with your customers, gradually.
The following table shows the association between various product versions and the Brightspace APIs and services they offer. Each table column shows, for a major LMS platform release version:
The earliest and latest supported API contract versions provided either by an individual product component along with that product component’s release version (first six rows), or by the overall Learning Suite release version (ext APIs). (Note that an individual product component may also still offer unsupported, obsolete, API contract versions older than are noted in the table.)
Where a product component introduces a new API contract with a minor platform release version, this additional support gets noted (for example, LE added the 1.75 API contract as of LMS v20.24.5).
Suite 20.26 |
Suite 20.25 |
Suite 20.24 (legacy) |
|
|---|---|---|---|
Learning Platform (lp) |
20.26.10+: 1.46* to 1.48*, 1.49 to 1.64
|
20.25.12: 1.46* to 1.48*, 1.49 to 1.55
|
20.24.12: 1.46* to 1.48*
|
Learning Environment (le) |
20.26.10+: 1.75* to 1.81*, 1.82 to 1.100
|
20.25.12: 1.75* to 1.81*, 1.82 to 1.90
|
20.24.11-12: 1.75* to 1.81*
|
Learning Repository (lr) |
20.26.1+: 1.3 |
20.25.1-12: 1.3 |
20.24.1-12: 1.3 |
ePortfolio (ep) |
20.26.1+: 2.5 |
20.25.1-12: 2.5 |
20.24.1-12: 2.5 |
Awards Service (bas) |
20.26.3+: 1.3*, 1.4 to 1.6
|
20.25.9-12: 1.3*, 1.4 to 1.5
|
20.24.4-12: 1.3*
|
Brightspace For Parents (bfp) |
20.26.1+: 1.0 |
20.25.1-12: 1.0 |
20.24.1-12: 1.0 |
Extensibility (ext) |
20.26.1+: 1.3 |
20.25.1-12: 1.3 |
20.24.1-12: 1.3 |
Note
Marked with an asterisk (‘*’); as of Suite 20.26.1’s release (January 2026), the API contracts introduced with Learning Suite 20.24 have become deprecated. You should plan to move off these routes with all due priority. Note that the latest API version is always fully supported.
Marked with a caret (‘^’); as of Suite 20.26.1’s release (January 2026), the API contracts introduced with all versions of the Learning Suite prior to 20.24 have become obsolete: they may or may not still be present on your back-end service, and will not receive any support by D2L. You should move off the routes in these contracts immediately and adopt the versions of these routes in newer, supported contracts. Note that the latest API version is always fully supported.
Extensibility APIs tie to the overall Learning Suite release version.
LTI support¶
Brightspace also implements the LTI standard as an LTI platform, to provide third-parties with a way to, as an LTI tool, integrate their services with Brightspace’s user experience in a standards-based way incorporating robust, service-to-service trust.
Brightspace supports several versions of LTI:
Prior to Suite 20.19.9’s release, Brightspace supported LTI 1.0 and LTI 1.1.1.
With the release of Suite 20.19.9, Brightspace added support for LTI 1.1.2.
With the release of Suite 20.19.10, Brightspace added support for LTI Advantage Complete (LTI 1.3 core, Assignment & Grade Services v2, Deep Linking v2, and Names & Roles Provisioning Service v2).
With the release of Suite 20.21.4, Brightspace added support for the LTI Dynamic Registration specification.
With the release of Suite 20.24.7, Brightspace added support for the LTI Platform Notification draft specification.
With the release of Suite 20.25.9, Brightspace added support for the LTI Asset Processor draft specifications.
Support¶
We provide support for Brightspace extensibility through a number of support paths, depending upon the nature of your issue or question.