1. Licensing Requirements
Your school requires:
- Access to the TASS REST API (latest version)
- A configured API User (Endpoint User)
- Generated Client Key & Client Secret
- Appropriate endpoint permissions configured per module
TASS API access is typically included within your standard TASS subscription.
Security Notes
- API access is controlled per user and per endpoint
- Credentials are generated securely and cannot be retrieved again after issue
- Do not share credentials via email
2. Setup Process
Step 1 – Create API User in TASS
- Log into TASS.web
- Navigate to:
System Admin → Utilities → API Endpoint Maintenance - Select “Add New User”
Configure the following:
- User Name – Unique identifier (e.g.
RollCall_API) - Purpose – e.g. RollCall Attendance Integration
- Contact Name / Email / Phone
- Enabled – ✅ Must be enabled
- Companies – Add relevant school company codes
- Endpoints – Select required endpoints (Please refer to Step 2)
? Best practice: Create a separate API user per integration for better control.
Step 2 – Configure Required Endpoints
When adding endpoints to the TASS API User, schools should grant RollCall access to the data areas required for the integration.
At a minimum, this usually includes endpoints for:
- Student details
- Parent / guardian details
- Student-parent relationship links
- Address details
We require:
getStudentsgetCommunicationRulesDetails
Step 3 – Generate API Credentials (Key & Secret)
- In the API user list, click the ? Key icon
- Generate:
- Client Key
- Client Secret
- A secure email is sent with a temporary retrieval link
Step 4 – Test API Access
Before sending details to RollCall, confirm:
- ✅ Successful authentication
- ✅ Student data retrieval
- ✅ Parent/contact data retrieval
- ✅ (Optional) Attendance endpoints accessible
All API communication occurs securely over HTTPS using JSON.
Step 5 – Submit Credentials Securely
RollCall will provide a secure e-Form link - LMS Integration Information Request
You will submit:
- API Key OR Client Secret (aK9fT2Lm8QwXzP4nR7sYc1Vb6HdJkE=+)
- Base URL (e.g.
https://your-school.tass.cloud) - App Code (RCALL)
- Company Code(s) (01)
- API Version (2 or 3 normally)
- Screenshot of TASS API User configuration
⚠ Do not send credentials via email.
Step 6 – RollCall Testing & Activation
RollCall will test the integration in a secure environment to:
- Validate API authentication
- Confirm student data sync
- Confirm parent/contact relationships
- Verify attendance endpoints (if applicable)
If any issues are identified, we will contact you before proceeding.
Step 7 – Go Live
Once validated:
- ✅ Integration is activated
- ✅ Nightly synchronisation begins
⏱ Typical activation timeframe:
A few business days after valid credentials are received
3. Key API Modules Used (RollCall Context)
Your integration will primarily rely on:
- Students
- Parents / Contacts
- Timetable
- Attendance
TASS provides a broad API library across student, finance, LMS, and reporting systems.
4. Troubleshooting
If data is not syncing correctly after activation:
Check the following:
- “Lives With” flag configured correctly
- Valid parent email addresses
- Address number (1, 4, or 5)
- Duplicate email conflicts
- Correct endpoint permissions enabled
5. Support
- TASS API Documentation:
https://api.developer.tassweb.com.au - TASS Support:
Contact via TASS Customer Hub - RollCall Support:
Raise a support request or contact your onboarding specialist
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article