Skip to main content

Attendance

Courses, trainings, workshops, shift starts. People show their badge or a QR code from an email, the organiser scans it, and the green screen confirms the attendance is recorded.

How it works#

  1. Each participant has a badge or an emailed QR code with their personal code.
  2. The organiser scans it at the door. The phone's deviceId tells your API which room it is.
  3. Your API records the attendance for the session running in that room now.

What your API checks#

  • The person is registered for this session.
  • The scan falls inside the session's time window (for example, from 15 minutes before the start).
  • The attendance isn't already recorded. A repeat scan should be a friendly green, not an error.

Example answers#

{ "status": "ok", "title": "Petra Horváthová", "message": "Fire safety training · room 3" }
{ "status": "ok", "title": "Already recorded", "message": "Checked in at 08:52", "backgroundColor": [0, 90, 140] }
{ "status": "failed", "title": "Not registered", "message": "This badge isn't on the list for this session" }

Settings#

Badges printed with Code 128 plus QR codes in emails, and nothing else.

{  "app": "scan2check.com",  "settings": {    "apiUrl": "https://api.example.com/attendance",    "symbols": [      "qr",      "code128"    ],    "autoScanTimeout": 1500  }}

Open in configurator — loads these settings so you can put in your own API URL and generate the QR code.

Watch out for#

  • A badge is not a person. The scan proves someone showed this badge, not who they are, nor how long they stayed. If that matters, have the organiser look at the person, or scan again on the way out.
  • Screenshots get passed around. A QR code in an email is easy to forward. Show the name in the green message so the organiser can compare it with the person in front of them.
  • "Which session?" Scans from the same room on the same day belong to different sessions. Decide it from the room (deviceId) and the time, not from the code alone.