Integrations
A clear approach to district-approved integrations.
Cymbari uses a vendor-neutral integration model so district systems can connect without one vendor's data structure defining the entire platform.
Integration foundationConnector availability varies
| System / Standard | Status | Current Cymbari position |
|---|---|---|
| OneRoster | Foundation ready | OneRoster-ready entity mapping with planned CSV and REST integration paths. |
| Ed-Fi | Foundation ready | Ed-Fi-compatible mapping strategy and version metadata. Cymbari does not currently claim Ed-Fi certification. |
| Synergy | Planned / district-specific | Planned connector for authorized district configurations. |
| PowerSchool | Planned | Planned SIS connector through Cymbari's common integration framework. |
| Infinite Campus | Planned | Planned SIS connector through Cymbari's common integration framework. |
| Google Classroom | Planned | Planned classroom and coursework connector, subject to district authorization and required platform permissions. |
| Canvas | Planned | Planned LMS connector through Cymbari's common integration framework. |
| EduClimber | Planned / district-specific | Planned assessment and intervention-data connector for approved district use. |
A planned connector is not yet generally available and does not imply approval by any district.
Controlled options when a direct API is unavailable
Cymbari is designed to prefer district-approved automated integrations while preserving controlled alternatives when a direct API is not available.
1
Approved API
2
OneRoster
3
Approved CSV
4
Secure universal import
5
Manual setup