> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/6.0/6.1/app-registration/schoology.md). # Schoology ### Get your consumer key and secret Log in to your Schoology server. Look at the top navigation bar and go to *Tools > School Management*. In the new screen, click on *Integrations* in the left menu. Now click on the API tab. You should see your consumer key and secret. The secret is hidden, so you have to use the *Reveal Existing Secret* option.

Integrations screen with the consumer key and secret.

### Configure the authentication values in Appmixer Log into the Backoffice and go to the *Services* section. Add a new service configuration named `appmixer:schoology`. After it is created, add the following configuration values:

Here is the explanation for each value: * **baseUrl:** The API base URL. Usually is , but there are some cases where it could be different. * **consumerKey and consumerSecret:** The consumer key and secret we got from the Schoology server. * **domain:** The subdomain part from your server. For example, if your server URL is **, then the domain value is just an *example*. --- # 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://docs.appmixer.com/6.0/6.1/app-registration/schoology.md?ask=&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.