Skip to main content
OneRoster File Structure

Build and format a OneRoster file

Jeremy Brown avatar
Written by Jeremy Brown
Updated over a week ago

ExploreLearning supports rostering integration through OneRoster v1.1 for LTI (Learning Tools Interoperability) and SAML (Security Assertion Markup Language) enabled districts. This article covers the basic requirements of the OneRoster standard we follow to provide a seamless user experience in Gizmos, Reflex, Frax and Science4Us.

OneRoster files are often pulled by a district from their Student Information System (SIS), as SIS files are pre-set to the OneRoster format. The district sends the OneRoster files to ExploreLearning via a Secure File Transfer Protocol (SFTP).

OneRoster Standard

  • Rostering data must be saved as Comma-Separated Values (CSV) files

  • File Names are case sensitive

  • File Names cannot deviate from the required standards provided

  • Columns cannot be relocated or removed

  • All Header Names and Content Values are case sensitive

  • No Metadata* columns allowed

    * Data providing information about one or more aspects of the data; it is used to summarize basic information about data that can make tracking and working with specific data easier.

  • The CSV files must be at the root level and sent in a .zip file called

Gizmos, Reflex, Frax and Science4Us require five CSV files

  1. users.csv

  2. classes.csv

  3. enrollments.csv

  4. orgs.csv

  5. academicSessions.csv

For questions about our products or setting up a system integration for your district, please contact your Account Representative, or you can contact our Customer Support team via the following methods:

Phone: USA/Canada 866.882.4141 Option 2, Option 5

Did this answer your question?