Edlink's integration with iSAMS synchronizes roster and related structural data via the iSAMS Batch API (xml.ashx), then maps that data into Edlink's unified models.
Single Sign-On (SSO)
SSO is not currently supported.
Edlink supports Single Sign-On (SSO) via isams using OAuth. This provides seamless access to connected platforms for schools by allowing user to login with their isams credentials.
Rostering
Edlink imports rostering data from iSAMS, including people (students, staff/teachers, and guardians), classes, enrollments, courses, subjects, departments, sessions (terms), facilities/rooms, and periods.
iSAMS classes map to Edlink classes. Student enrollments come from class–student links; teacher enrollments are derived from teacher IDs on each class.
Extended Rostering
The current integration focuses on core and structural rostering (including periods and class→period linkage via curriculum blocks). Attendance and behavioral incidents are not synced from iSAMS today.
See below for the full list of supported models.
Managing Coursework and Grades
iSAMS Batch rostering does not sync assignments, submissions, or gradebooks through Edlink.
Enrichment with iSAMS
iSAMS is typically used as a primary SIS source for rostering. Using iSAMS as a secondary enrichment source is not documented as supported at this time.
Special Features
- Batch API + OAuth: Sync uses OAuth 2.0
client_credentials(scopeapiv1) plus the Batch API key on each request. Legacy apiKey-only auth is not supported. - Method allocation: Each Batch method must be allocated to the school's API client in iSAMS API Services Manager. Missing methods fail validation or (for required methods) the sync.
- Optional methods: Contact types, timetable periods, and curriculum blocks are fetched when allocated; if not, sync continues without that enrichment (e.g. classes without period links).
- Single-school model: District and school records are synthesized from the Edlink team/source context rather than pulled as separate iSAMS org entities.