Attendance Data - How Does it Work?

API Access

To request early access to Clever's Attendance API, please fill out this form. Once approved, you will be granted attendance data scopes as well as access to a Clever-managed sandbox district containing demo attendance data.

District Ingestion

To send attendance data to Clever, and subsequently to your application, districts must first sync attendance data to Clever. For this current iteration of attendance data ingestion, districts must use SFTP to sync CSV files exported from their SIS. Other forms of automated syncing do not currently support attendance data imports. To learn more about sync types, see this Help Center article.

attendance.csv

The columns for attendance.csv are listed below:

Student_id
School_id
Section_id
Attendance_date (YYYY-MM-DD)
Attendance_type (daily, section)
Attendance_status (absent, tardy, present)
Excuse_code
Sis_id

Incremental Updates

Our Attendance API is designed for incremental updates. Districts are not required to upload their full attendance history with every sync. Instead, the system accepts new or modified attendance records, streamlining data transfer and minimizing load. This allows districts to update attendance data efficiently without needing to resend unchanged records.

Retention Policy

Clever will store attendance records for 6 months past the date indicated in the attendance_date field.