How the Integration Works
Edlink's integration with Toddle facilitates synchronization of key educational data. The integration leverages Toddle API endpoints to pull data and transform it into Edlink's unified data model. Toddle objects are mapped to Edlink objects through a standardized transformation process.
Assignments and submissions are handled live through the Toddle API (not via roster sync). See Supported Functionality for supported operations.
Data Mapping
| Toddle Model | Edlink Model |
|---|---|
| Grade Period | Session |
| Subject | Subject |
| Subject | Department |
| Course | Class |
| Student, Staff | Person |
| Course Student, Course Staff | Enrollment |
| Assignment | Assignment |
| Student Assignment | Submission |
Limitations
- Toddle sources must have a "curriculum". Curriculums are the parent entities to all others (i.e. courses, students, etc).
- Grade passback and assignment create/update require a
curriculum_program_id. If the org has exactly one curriculum, Edlink resolves it automatically; otherwise setcurriculum_program_id(orcurriculumProgramId) on the source configuration, or passproperties.toddle.curriculumProgramIdwhen creating an assignment. - Creating an assignment requires a valid
session_id(ToddlegradingPeriodId). - Assignments cannot be deleted via the Toddle API.
- Submission IDs are synthesized as
{assignmentId}-{studentId}because Toddle has no standalone submission ID. - Grade passback requires the submission to have been fetched from Toddle first (so
properties.toddle.academicTermIdis present). - Only
grade_pointsandgrade_commentcan be written back. Other assessment tools (rubrics, checklists, grade scales, etc.) are read-only. - Student submission of attachments, reclaiming, returning, and file downloads are not supported by the Toddle API.
Custom Field Mapping
The following fields can be custom-mapped in our dashboard UI:
- system roles
- roles