> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/commons.md).

# Commons

Canvas Commons includes a REST API for accessing and modifying data externally from the main application, in your own programs and scripts. This documentation describes the resources that make up the API.

Most API requests require a valid session. To create a session, see the Create a Session Documentation under the the Sessions section.

API requests are limited at a rate of 2500 requests per hour per user.

The endpoints have regional hosts, pick yours from the list below based on you region.

* US/LATAM:
  * <https://lor.instructure.com/api>
  * <https://lor-beta.instructure.com/api>
* EMEA (hosted in Germany):
  * <https://commons.eu-central.canvaslms.com/api>
  * <https://commons-fra-beta.instructure.com/api>
* Canada:
  * <https://commons.ca-central.canvaslms.com/api>
  * <https://commons-yul-beta.instructure.com/api>
* Australia/NZ (hosted in Australia):
  * <https://commons.sydney.canvaslms.com/api>
  * <https://commons-syd-beta.instructure.com/api>
* Asia Pacific (hosted in Singapore):
  * <https://commons.singapore.canvaslms.com/api>
  * <https://commons-sin-beta.instructure.com/api>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developerdocs.instructure.com/services/commons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.