Schoology
by PowerSchool
A K-12 LMS (now PowerSchool). REST API v1 with OAuth signing, plus Realtime 'Event Triggers' (webhook-style event objects). API access is gated by district admins.
Direct integrations
Native integrations you connect from inside the LMS — typically an OAuth "Connect" flow, with no external middleware.
Supported — Integrates via LTI and the PowerSchool ecosystem (SIS sync); third-party apps via the App Center.
| Integration | Category | Type | Notes |
|---|---|---|---|
| LTI 1.3 / LTI Advantage | Interoperability | lti |
External tool integration. |
| PowerSchool SIS | SIS | api-key |
Student information system sync. |
| Google Drive / Microsoft OneDrive | Productivity | oauth |
Attach cloud files. |
| SAML 2.0 SSO | Identity | saml |
Single sign-on. |
Middleware support
Third-party automation platforms (iPaaS) that connect this LMS to thousands of other apps without code.
Supported — Integrations run through the REST API (OAuth-signed); no first-party iPaaS app.
| Platform | Supported | Details |
|---|---|---|
| Zapier | No | Integrate via the REST API. |
| Make | Yes | Via HTTP modules against the REST API. |
| Pabbly Connect | Yes | Via HTTP against the REST API. |
| n8n | Yes | Via the HTTP Request node against the REST API. |
| Microsoft Power Automate | No | |
| Workato | No | |
| Tray.io | No |
API
Programmatic access to the LMS. Endpoints below are a documented subset — always check the vendor's official reference for the complete, current list.
Supported — REST API for users, courses, sections, enrollments, groups, and grades. Requests are OAuth-signed. Paths below are representative.
| Type | REST |
|---|---|
| Version | v1 |
| Authentication | OAuth (two-legged HMAC-signed; three-legged available). API access enabled per-user by the district Schoology admin. |
| Base URL | https://api.schoology.com/v1 |
| Format | JSON or XML |
| Rate limit | Per-key throttling; see developer docs. |
| Docs | https://developers.schoology.com/api-documentation/rest-api-v1/ |
Endpoints
Users
| Method | Endpoint | Description |
|---|---|---|
| GET | /users |
List users |
| GET | /users/{id} |
Get a user |
| POST | /users |
Create users |
Courses
| Method | Endpoint | Description |
|---|---|---|
| GET | /courses |
List courses |
Sections
| Method | Endpoint | Description |
|---|---|---|
| GET | /courses/{id}/sections |
List sections of a course |
Enrollments
| Method | Endpoint | Description |
|---|---|---|
| GET | /sections/{id}/enrollments |
List enrollments in a section |
| POST | /sections/{id}/enrollments |
Enroll a user in a section |
Grades
| Method | Endpoint | Description |
|---|---|---|
| GET | /sections/{id}/grades |
Get grades for a section |
Groups
| Method | Endpoint | Description |
|---|---|---|
| GET | /groups |
List groups |
Webhooks
Outbound HTTP callbacks the LMS sends to your endpoint when events occur, with their supported event types and security model.
Supported — Schoology's API includes Realtime 'Event Triggers' — you register to receive event objects when changes occur, rather than polling. Delivery/authenticity is tied to the OAuth-signed API relationship.
Docs: https://developers.schoology.com/api-documentation/
Security: HTTPS endpoint OAuth-signed API relationship
| Event | Description |
|---|---|
User events | User created/updated |
Enrollment events | Enrollment changes in sections |
Grade events | Grade changes |