✅ Add Attendance

Updated 12 Oct 2026 by Danish

The addAttendance mutation records a student's attendance at a meeting. The attendance is always stored; the warnings field lists any reasons it will not count toward the student's course requirements yet.

Input Parameters

Parameter	Type	Description
`attendance`	AttendanceInput!	Attendance details including student ID, meeting resource ID, and an optional timestamp.

Input Object: AttendanceInput

Field	Type	Description
`studentId`	String!	ID of the student whose attendance is being recorded.
`resourceId`	String!	ID of the meeting resource the student attended.
`timestamp`	String	Optional timestamp of the attendance record.

Response Fields

Field	Type	Description
`activityId`	String!	Unique identifier of the recorded attendance activity.
`assets`	[AssetUpload!]!	List of assets uploaded as attendance proof.
`evidenceAssets`	[AssetUpload!]!	List of evidence assets attached to the attendance record.
`warnings`	[ActivityWarning!]!	Non-fatal problems with the recorded attendance — the reasons it will not count toward the student's course requirements yet. Empty when the attendance counts.

Object: ActivityWarning

Field	Type	Description
`code`	String!	Stable machine-readable code (see below). New codes may be added; treat unknown codes as informational.
`message`	String!	Human-readable explanation for logs and support. Informational only: the wording may change, so branch on `code`, not on this text.

Warning Codes

Code	Meaning
`RESOURCE_NOT_VERIFIED`	The meeting resource is not `VERIFIED` yet, so the attendance does not count yet.
`RESOURCE_HAS_NO_WORKLOAD`	The meeting resource has no workload set, so the attendance does not count toward course requirements yet.

✅ Add Attendance

🚀 Request (Try It)