Implementation Details
API Used
Edlink’s Blackbaud rostering and directory integration uses Blackbaud SKY API only (api.sky.blackbaud.com), authenticated with OAuth 2.0 and a subscription key.
Edlink does not use Blackbaud’s legacy Education Management SDK surfaces (ON API or ODBC/VPN / direct SQL access). Blackbaud’s announced end of support for those legacy tools on March 31, 2027 does not affect Edlink-connected schools or applications—no migration or configuration change is required for the Edlink connection on that deadline.
Coursework / grade passback (when enabled) uses Blackbaud’s OneRoster gateway with OneRoster keys; see Grade Passback below.
Data Mapping
| Blackbaud Entity | Edlink Entity |
|---|---|
| User | Person, Agent |
| Academic Section | Class |
| Roster | Enrollment |
| Year | Calendar |
| Term | Session |
| Course, Roster | Course |
| Level | School |
| Schedule | Day, Period |
| Attendance | Meeting, Attendance |
| Department | Department, Subject |
| Building, Dorm, Venue | Facility, Room |
| Transportation Type | Asset, Vehicle |
| LineItem | Assignment |
| Result | Submission |
Grade Passback
Grade Passback for Blackbaud is implemented using the OneRoster API. If you do not provide OneRoster keys, grade passback will not work. If you do not require grade passback, you do not need to provide OneRoster keys, but it is still recommended that you provide them for future use cases.
Assignment Notes
- Assignments are associated with the lead section.
- Assignments require categories in Blackbaud.
- Deleting assignments is not allowed in Blackbaud.
Submission Notes
- Only fully graded assignments are allowed in Blackbaud.
Custom Field Mapping
The following fields can be custom-mapped in our dashboard UI:
- roles
- gender identities
- attendance flags
- grade levels