Connect your student information system.
nOS reads your student information system and returns the finished schedule to most.
The full list
Every system sends the same data in: students, teachers, courses, sections, rooms and current enrollments. Course requests come from systems with a request feed, and as a spreadsheet from those without one (OneRoster has none). Pull again whenever you like, and you see what changed before it lands.
If you edited a student, class or request, your edit stays unless the system changed that field too; then nOS asks which to keep. No live connection yet? Upload a OneRoster system's export, as its .zip or its CSV files, into the same review.
| System | How it connects | Administrator setup | Finished schedule returns | How delivery is confirmed |
|---|---|---|---|---|
| PowerSchool | OAuth 2.0 client credentials | A server or district administrator installs and enables a PowerSchool plugin that grants the read permissions, then copies that plugin’s own OAuth Client ID and Client Secret. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| Blackbaud | Sign in with the vendor, or API credentials | Register a confidential SKY application, add a School API subscription, and have a user with Marketplace permission connect the application to the school and approve its scopes. | Yes, over the API | The system’s own response, on the verify page |
| Veracross | OAuth 2.0 client credentials | A Veracross system administrator creates a client-credentials OAuth application in Data API v3 with the listed scopes and copies its Client ID and Client Secret. | Yes, over the API | The system’s own response, on the verify page |
| Aeries | REST with an API certificate | A district administrator creates a dedicated API certificate under Security → API Security with Read on each listed security area, plus the Insert and Update rights a send needs. | Yes, over the API | The system’s own response, on the verify page |
| Infinite Campus | OneRoster 1.1 (base URL, client ID and secret) | Infinite Campus must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| FACTS | OneRoster 1.1 (base URL, client ID and secret) | FACTS SIS must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Skyward | OneRoster 1.1 (base URL, client ID and secret) | Skyward must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| Synergy | OneRoster 1.1 (base URL, client ID and secret) | Synergy SIS must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| Focus | OneRoster 1.1 (base URL, client ID and secret) | Focus must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Rediker | OneRoster 1.1 (base URL, client ID and secret) | A Supervisor turns on Send Data for OneRoster Integration in Administrator's Plus's TeacherPlus Setup & Sync Manager and copies TeacherPlus's OneRoster Client ID, Client Secret and Token URL, or runs AdminPlus's OneRoster Export and uploads its files. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| ClassLink | OneRoster 1.1 (base URL, client ID and secret) | ClassLink must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Frontline | OneRoster 1.1 (base URL, client ID and secret) | Frontline must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Genesis | OneRoster 1.1 (base URL, client ID and secret) | Genesis must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
| Illuminate | OneRoster 1.1 (base URL, client ID and secret) | Illuminate must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Sycamore | OneRoster 1.1 (base URL, client ID and secret) | Sycamore must turn on its OneRoster 1.1 REST provider for the district and issue a Base URL, an OAuth Client ID and a Client Secret with the read permissions enabled. | No, read-only | Nothing goes back |
| Canvas | Access token; the schedule goes back as an SIS Import CSV | An account that can read the whole roster creates a personal access token under Profile → Settings → Approved Integrations. | Yes, as its own import file | The system’s own response, on the verify page |
| QuickSchools | REST with an API key | An administrator turns on the App Developer Console and creates a dedicated API key. | Yes, over the API | The system’s own response, on the verify page |
| Clever | REST with a district token | The district shares its data with the nOS app in Clever; nOS support then sends the district token to paste into nOS. | No, read-only | Nothing goes back |
| SchoolRunner | REST with a username and password | SchoolRunner support confirms the tenant has the REST API and issues a read-only API username and password. | As a reviewed handoff file | Your administrator confirms the import; the download alone is not proof |
An administrator sets it up
Your SIS administrator issues the credentials (a base URL and client keys, an API key, or a sign-in with the vendor), pastes them into Settings, and tests the connection before anything is imported. We’re happy to do it with you on a call.
What happens when you send
Sends are additive: nOS creates and updates sections, adds enrollments and sets rooms. Nothing in your system is deleted, and you approve the whole list first. For PowerSchool and some others, the same list becomes a reviewed handoff file your administrator imports. The table above shows which systems get a file and which get nothing back yet.
How you know it landed
An API write or a submitted import file is confirmed by the vendor's own response, on the verify page. A handoff file is confirmed when your administrator says they imported it; the download by itself is never treated as delivery.
Rediker, step by step
For schools on Rediker's Administrator's Plus. Rediker has no way to take a schedule over the internet, so it goes back as a file Administrator's Plus already knows how to import. nOS walks you through every step on screen, and the download carries the same steps as a notes file.
1. Bring your data in
With keys: in Administrator's Plus, turn on Send Data for OneRoster Integration (Tools, TeacherPlus Setup & Sync Manager). Then paste the Client ID, Client Secret and Token URL from TeacherPlus (Settings, Integrations, OneRoster) into nOS.
Without keys: run Administrator's Plus's OneRoster Export and upload the files it writes.
Either way, you review everything before it lands.
2. Send the schedule back
Download the files from nOS. In Administrator's Plus, set next year as the scheduling year, then open Tools, Interfaces, TimeTabler and choose TTExport.TXT. Every class arrives with its meeting times, teacher and room. Administrator's Plus saves a backup of its schedule files before it imports, and it matches each course by its exact name, so nOS never shortens one.
3. Place your students
Administrator's Plus imports classes, not student schedules. The download lists every student's classes, class by class, ready for Batch Add Schedule in AdminPlus.com or for Rediker support to load. Then tell nOS you imported the files.
Your student information system stays the system of record for enrollment, grades, attendance and reporting. nOS takes over only the scheduling.
The names of student information systems on this page are trademarks of their owners. nOS is not affiliated with, endorsed by or sponsored by any of them.
Connect yours in the trial.
Bring your SIS administrator and the credentials they issue.