Integration Platform Overview

The Edlink Integration Platform helps edtech developers build and manage integrations to the LMS, SIS, and identity systems schools already use. Instead of building and maintaining a separate integration for every platform, developers integrate once with our Unified API and gain access to a wide range of data providers through a consistent data model and set of endpoints.

Schools run on a variety of systems like Canvas, Clever, Google Classroom, Skyward - each with its own APIs, authentication flows, and data quirks. The Unified API exists to absorb that complexity so product teams can focus on building great experiences for teachers, students, and administrators.

Edlink normalizes data from these sources into a common model, handles authentication and syncing, and gives both companies and schools tools to control what data is shared. The result is faster time-to-market for edtech companies and a safer, more manageable integration process for schools.

For Edtech Companies

Software developers are the primary audience for the Unified API. A typical integration workflow looks like this:

1. Sign up for Edlink and create an application in the dashboard.
2. Build against the API using sandbox data to test rostering, SSO, grade passback, and other workflows.
3. Onboard production schools and go live.

Developers can use Edlink to get users signed in with SSO, ingest roster & attendance data, send and receive coursework and grades, and more.

For Schools

Edlink allows schools to quickly and safely establish LMS and SIS integrations with vendors that they use. It also provides a dashboard for IT administrators to manage these integrations and the data that is shared between systems.

Schools do not call the Unified API directly. Instead, IT administrators connect their LMS or SIS to Edlink through a guided onboarding flow — usually triggered by an edtech vendor — and then manage those connections from the Edlink dashboard. The API is what makes that connection useful on the vendor's side.

Edlink is middleware between your school's systems and the edtech products you use. It is not a tool that gets rolled out to teachers and students — it works in the background to help vendors connect to your LMS, SIS, or identity provider safely and consistently.

When a vendor asks you to integrate through Edlink, here is what to expect:

1. You receive an onboarding link from the vendor (or find one in their product).
2. You complete a short setup flow — typically 5 to 10 minutes — to connect your data provider and approve the integration.
3. You manage the connection and data sharing settings from the Edlink dashboard going forward.

Edlink gives IT administrators more control over integrations than most direct vendor connections provide. You can see which applications are connected, review what data is being shared through Sharing Rules, and pause or revoke access when needed.