LogoLogo
6.1
  • Docs
  • Connector Configuration
  • Knowledge Base
  • Changelog
6.1
  • Introduction
  • Getting Started
    • Build and Publish an Integration
    • Build and Run an Automation
    • Build and Run an AI agent
    • Build a Custom Connector
    • Embed into Your Application
    • Monitor & Troubleshoot
    • Access Appmixer REST API
    • Install and Update Connectors
    • Connector Configuration
    • Handle Flow Errors
    • Use App Events
    • End User Guide
  • API
    • Authentication
    • Flows
    • Apps
    • Accounts
    • User
    • Insights
    • Files
    • Data Stores
    • Connector Configuration
    • People Task
    • ACL
    • Charts
    • Config
    • Modifiers
    • Public Files
    • Unprocessed Messages
    • Variables
  • Building Connectors
    • Flow
    • Component
    • Basic Structure
    • Manifest
      • name
      • label
      • icon
      • description
      • auth
      • inPorts
      • outPorts
      • properties
      • quota
      • tick
      • private
      • webhook
      • httpRequestMethods
      • state
      • author
      • marker
      • localization
      • firePatterns
    • Behaviour
    • Dependencies
    • Authentication
    • Quotas & Limits
    • Example: twilio.SendSMS
    • Example: Webhook Trigger
  • Appmixer UI SDK
    • Introduction
    • Installation
    • Quick Start
    • Constructor
    • API Module
    • UI & Widgets
      • Flow Manager
      • Designer
      • Insights Logs
      • Insights Chart Editor
      • Insights Dashboard
      • Accounts
      • Storage
      • People Tasks
      • Connectors
      • Integrations
      • Wizard
    • Custom API
  • Customizing Embedded UI
    • Custom Theme
    • Custom Strings
    • Custom Component Strings
  • Appmixer Backoffice
    • Getting Started
    • System Configuration
  • Appmixer CLI
    • Getting Started
    • OpenAPI Connector Generator
      • Getting started
      • Open API Extensions
      • Examples
  • Appmixer Self-Managed
    • Installation Docker Compose
    • Installation AWS ECS
    • Getting Started
    • Authentication Hub
    • Additional Configuration
    • Appmixer Architecture
    • Appmixer Deployment Models
  • Tutorials
    • Appmixer Virtual Users
    • Flows Metadata & Filtering
    • Access Control
    • Sharing Flows
    • People Tasks
    • Customizing modifiers
  • App Registration
    • Airtable
    • ActiveCampaign
    • Asana
    • Azure Cognitive Services
    • Blackboard
    • DeepAI
    • DocuSign
    • Dropbox
    • Freshdesk
    • Google
    • Highrise
    • Hubspot
    • Jira
    • Jotform
    • LinkedIn
    • Mailchimp
    • Microsoft
    • Microsoft Dynamics 365 CRM
    • Monday
    • Open AI
    • Pipedrive
    • Quickbooks
    • Redmine
    • Salesforce
    • Schoology
    • Screenshot API
    • ServiceNow
    • Slack
    • Trello
    • Typeform
    • Twilio
    • Twitter
    • Utilities
      • AI
      • Email
      • Language
      • Tasks
      • Test
      • Weather
      • AppEvents
    • Xero
    • Zendesk Tickets
    • Zendesk Chat
    • Zoho
  • Connectors
    • Connector Request
Powered by GitBook
On this page
  • Get your consumer key and secret
  • Configure the authentication values in Appmixer

Was this helpful?

Export as PDF
  1. App Registration

Schoology

PreviousSalesforceNextScreenshot API

Was this helpful?

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.

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 https://api.schoology.com/v1, 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 https://example.schoology.com, then the domain value is just an example.

Integrations screen with the consumer key and secret.
Configuration values for Schoology