Hardware & Service Integration
RollCall + Custom card provider (API)
Update student card codes from any card system, or your own script, through RollCall's card-update API.
Book a demoWhat the Custom card provider (API) integration does
You don't have to use a card provider at all. RollCall's card-update endpoint is a public, token-secured API that any card system, or a school's own script, can call to keep student card codes current. Card codes flow one way into RollCall, keyed by student number, so cards work for bus tap-on and tap-off without anyone re-keying numbers by hand.
Data flow
One-way syncYour card system or script is the source of card codes. Each update posts a student number and card code to RollCall's secure card-update endpoint, ready for tap-on and tap-off scanning. This is the same provider-agnostic endpoint PPC and MonitorWA use.
| Data | Direction |
|---|---|
| Card code updateStudent number and card code posted to RollCall's secure card-update endpoint, one POST per card | Your system → RollCall |
| Card formatSend the MIFARE and NFC card codes read by RollCall's bus scanners | Your system → RollCall |
What you need
- A RollCall account with student records in place
- A card system or in-house script that can send an HTTPS POST
Setup
Generate the integration token in RollCall
In RollCall, generate the secure third-party integration token that authorises card-code updates for your school.
Point your system at the endpoint
Configure your card system or script to POST each student's number and card code to RollCall's card-update endpoint, one request per card, authorised with your token.
Send a test update
Post a single test card update to confirm the code lands against the right student, then roll it out across your cards.
Custom card provider (API) integration FAQs
More Hardware & Service integrations
See it in your school
Book a demo and we'll show you the Custom card provider (API) integration end to end.
No obligation, see how RollCall fits your existing stack.