Skip to content

Attender API

Attendance verification for schools and teams. In development, not yet published.

Not yet published

The Attender API is in development. There is no public endpoint, no base URL and no key issuance for it yet. This page exists so you know what is coming rather than guessing. Nothing below is callable today.

Attender is the attendance product: it verifies who was present, when, and produces the record a school or employer can actually rely on. The web application is live at attender.karmat-hq.com. What is not yet available is a programmatic interface to it.

What exists today

SurfaceStatus
Web applicationLive. Enrolment, session capture, roster management and reporting.
HTTP APIIn development. Not published, not documented, no keys issued.
WebhooksPlanned, following the same HMAC-signed pattern as the diagnostics API.

What the API is expected to cover

We are designing it to match the two APIs already published: the same X-API-Key header, the same reviewed access flow, the same error semantics, so an integration you have already built against Seerah AI or Optical Diagnostics will feel familiar.

  • Enrolment. Register a person and their reference capture against an organisation.
  • Verification. Submit a capture and receive a match decision with a confidence score.
  • Sessions. Open and close an attendance window, and read the roster state for it.
  • Reporting. Query attendance over a date range for a person, a group or an organisation.

Biometric data carries obligations

Attendance verification means handling biometric templates, which most jurisdictions regulate more strictly than ordinary personal data. Including Nigeria's NDPR. Consent has to be explicit and informed, and there must be a non-biometric alternative for anyone who declines. We would rather ship this interface late than ship one that makes it easy for an integrator to get that wrong.

In the meantime

If you have a use case that needs programmatic attendance data now, tell us what it is. It directly shapes what we build first, and we can sometimes serve it another way while the API is in progress.