Developer tools¶
As the Brightspace API is language-platform neutral, you can choose the development and testing tools that are most familiar to you, provided they have good support for making web requests.
HTTP requests. Your tools should give you good support for making HTTP requests with the following features:
Can properly support HTTPS, not just HTTP.
Can support use of the GET, DELETE, POST, and PUT HTTP methods.
For sending data to the back-end service, can properly support both data uploads using multipart/form-data (see RFC 1867) and multipart/mixed content types (see RFC 2388).
Note that a few common HTTP libraries and test tools do not give good high-level support for the multipart/mixed content type: in these cases, you may need to manually assemble HTTP requests headers and bodies before using your library to send the request.
Testing tools. Some language platforms can provide a convenient REPL (read-eval-print loop), and with fairly minimal effort you can use them for interactive testing with your back-end service.
Also, we recommend you consider using Postman, a market-leading web service API testing tool. You can find some Sample Postman Environments and Collections on the Brightspace Github organization. You can also find information on how to connect Postman to Brightspace in the Brightspace Developer Community.
Developer sites¶
In order to use the Brightspace API you will require a Brightspace site to work with. Here are the options available:
Developer Persona |
Notes |
---|---|
D2L Customers |
For development and testing purposes please work with your Brightspace Administrator to determine if a non-production instance of Brightspace is available. |
D2L Partners |
D2L makes test servers available as a service through our Partner program. Contact the D2L Partner team for more information. |