Which data intake method should you use?

Choose between creating or copying records in the UI, CSV import and export, and API integration.

integrationcsvapidirectory

Audience: Organization admins / academic admins / IT · Applies to: SaaS / private

Goal: Choose the right intake method without building a complex integration before it is needed.

How to choose

Scenario	Recommended	Why
Trial, pilot, one-off additions, or very few people	Create in the UI / copy selected records	Organization admins use Settings → Organization & intake; academic admins use Classes
Several classes with the same structure or several accounts of the same type	Copy selected records, then change identity fields	Reduces repeated entry; copied classes do not include members
One-time term setup, many people, no development resources	CSV	Download a template and receive clear validation feedback
Weekly or daily synchronization with an academic system or SIS	API	Supports incremental automation with fewer manual errors
Pilot first, then scale	Start with the UI or CSV, then move to API	Validate fields and class-code conventions first
Private deployment with an existing integration platform	Use API for primary data and UI / CSV for corrections	Keep master data in the integration platform and use the UI for quick corrections
Export a score snapshot only	CSV export	No API integration is required
Create tasks or retrieve results programmatically	API	Exports cannot provide continuous writes

Very few people and you need to start now? → Create or copy records in the UI. See Classes and teacher access.
No developers, and the roster is already in a spreadsheet? → CSV.
Need automatic weekly updates? → API.
Fields are not final yet? → Test a small sample in the UI or CSV first.