OneRoster Overview

Triand OneRoster API implements 1EdTech's OneRoster® API specification. The OneRoster® API allows districts to securely share roster information with third-party applications via a REST API.
Visit 1EdTech to learn more.

Triand OneRoster API Service is certified for both OneRoster v1.1 and OneRoster v1.2.

Access is district-scoped, secured with OAuth2, and read-only: each vendor's credentials reach only the data for the specific district that authorized them, only the fields covered by the scopes they were granted, and no data can be changed through the API.

All roster data originates in Arkansas eSchoolPlus (the district SMS) and is refreshed nightly: SMS tables → nightly district extract → Triand student record store → OneRoster transformation. Only currently-enrolled students with a valid State-ID, their current-year course sections, and Staff-Catalog teachers are rostered (home/private placements and prior-year history are excluded). The Data Dictionary maps every OneRoster field back to its originating eSchoolPlus table and column, and lists the full inclusion rules.

How the data flows: eSchool → Triand/OneRoster → API Vendor

Triand publishes a live, queryable OneRoster API — we do not send, push, or email data files to anyone using the OneRoster API. API vendors connect to the API and pull exactly the data they need, much like securely logging into a database.

eSchoolPlus

Arkansas district SMS — the system of record

nightly extract ↓

Triand OneRoster API

Refreshed every night by 11:00 pm CST

Every record carries a last-modified timestamp, so vendors can query only what changed (deltas).
Every record carries an active / tobedeleted status. tobedeleted records are removed after 7 days, which is how vendors learn a student has dropped a class or left a school.

vendor queries the API securely (deltas only) — no data files are sent ↓

API Vendor — e.g. Cambium Assessments

Queries and filters only the data they need, like securely logging into a database. Triand does not send any data files.

vendor builds import files ↓

Vendor System — e.g. TIDE

A vendor may create data files from the queried data and imports them into their own system.