TASS APIs
Overview
TASS APIs are created by TASS to allow third-party companies to connect to the TASS database.
These APIs are publicly available, so your school can use them to develop internally in a 'self-service' way, with all documentation and support provided through the GitHub community.
Anyone- whether a school or vendor- can use these APIS to build integrations with TASS. However, usage by non-approved integration partners is not certified. Some TASS APIs require partner certification, and certain functions are only accessible through Certified Integration Partners.
TASS APIs are typically used by third-party software vendors, developers, or anyone with moderate programming and scripting expertise. Whilst these organisations or individuals might handle the initial programming and deployment of the integration, all staff - teachers, business managers, and more - can benefit from the result.
From 2026, the TASS licensing model includes full API access for all customers. External and TASS APIs are now part of your school’s TASS license, so you no longer need to request additional API licenses to access them.
You can activate these APIs directly via the ‘External APIs’ and ‘TASS APIs’ tabs in the TASS.web System Admin > Utilities> API Gateway Maintenance program.
We encourage you to explore integration options through our Certified Integration Partner network or contact your Customer Success Consultant for tailored guidance.
About Certified Integration Partners
Some APIs require partner certification and are available only through Certified Integration Partners. These TASS APIs are marked ‘Yes’ in the Certified Integration Partners column below.
Certified integrations have been developed collaboratively between TASS and like-minded software providers within the education space, to deliver seamless online experiences to our mutual customers.
Certification is achieved through extensive ‘scenario based’ testing to ensure that:
the TASS API is sending the information required by the third-party system.
the third-party system receiving the data is consuming it correctly.
any data passed back to TASS adheres to TASS logic and structures.
Certified integrations are fully supported by TASS and the Customer Care team, and are only available through approved TASS Integration Partners.
These ‘off the shelf’ integrations are best for schools who want a ready to use, tried and tested approach to handling their data exchanges.
Refer to the relevant Matrices of Currently Certified Integration Partners for information on the endpoints for which each vendor is certified.
About Publicly Available APIs
In our endeavour to be a ‘solutions focused’ organisation and provide customers with greater control over their internal systems, the documentation for all TASS APIs is available publicly on GitHub.
The transparency that this platform provides means that customers can determine internally what they hope to achieve with their data and how they wish to use, share and represent it.
Development against the TASS APIs is very much a self-service approach, with all guidance and requests for assistance being provided through the GitHub community only.
About API Versions
The 'Version' listed for the API refers to the security methods used:
Version 2 | Data can be processed without any restrictions and is based on school providing access to the associated endpoints. |
Version 3 | Security Roles are required to use the API method, which restricts what information can be accessed. For specific information on API methods, their versions and any applicable permissions needed, visit our GitHub page. See ‘Version 3 APIs’ for a list of Certified Partners who use this version. Important! TASS recommends creating a new Security Role for each unique API integration. |
More information about API versions an how to use TASS APIs can be found here: https://github.com/TheAlphaSchoolSystemPTYLTD/api-introduction
TASS APIs
Name of TASS API | Description | Certified Integration Partners |
|---|---|---|
Accounts Payable Integration (Licence Code: API06) | This Version 2 public API supports third-party OCR scanning and workflow automation software, for the creation of Invoices in TASS.web Finance > Accounts Payable > Supplier Transactions > Invoices without the need for any manual data entry. The following information can also be extracted by this API:
Link to GitHub documentation. | Yes Certified Partners:
|
Assessment (Licence Code: API29) | This Version 3 public API allows users to retrieve the following information:
The API allows users to upload the following information:
The LMS Integration API must also be enabled to use this API. Link to GitHub documentation. | No |
Boarding (Licence Code: API10) | This Version 3 public API extracts the following information for students who have been flagged as a boarder within TASS.web:
Link to GitHub documentation. | Yes Certified Partners:
|
CeDe3 Integration (Licence Code: API09) | This private API is reserved for use by the Catholic Education Diocese. Contact Customer Care for access. | No |
Consent2Go Integration (Licence Code: API31) | This Version 3 private API allows integration between the third-party application Consent2Go and TASS. It allows Consent2Go users to retrieve the following information:
The API also allows Consent2Go to upload the following information back into TASS:
| Yes Certified Partners:
|
Data Upload Utility (Licence Code: API14) | This Version 2 public API mirrors the functionality available in TASS.web System Admin > Utilities > Data Upload Utility, but instead of updating data via a CSV upload, data is updated via direct passing of information into the database via the API. Link to GitHub documentation. | Yes Certified Partners:
|
Edumate Integration (Licence Code: API21) | This Version 2 private API extracts the following General Ledger-related information:
The following can be updated by this API:
Contact Customer Care for access. | Yes Certified Partners:
|
EmployeeHR (Licence Code: API13) | This Version 2 public API enables basic employee records to be submitted using third-party software to be entered into TASS.web Payroll/HRM > Employee/HR > Employee Information > Employees without any manual data entry. The following information can also be extracted by this API:
Link to GitHub documentation. | Yes Certified Partners:
|
General Ledger Analytics (Licence Code: API22) | This Version 3 public API extracts the following General Ledger-related information:
Link to GitHub documentation. | No |
Identity Management (IdM) (Licence Code: API23) | This Version 3 public API extracts the following information used with third-party Identity Management Providers:
The following is also able to be updated by this API:
For more information, refer to the 'Version 53 - IdM API' video. Link to GitHub documentation. | Yes Certified Partners:
|
LEQ Integration (Licence Code: API15) | This is a private API reserved for use by Lutheran Education Queensland. Contact Customer Care for access. | No |
Library Integration (Licence Code: API07) | This Version 3 public API extracts the following information required by third-party library management software:
Link to GitHub documentation. | Yes Certified Partners:
|
LMS Integration (Licence Code: API03) | This Version 3 public API extracts the following information required by third-party learning management system software:
Link to GitHub documentation. | Yes Certified Partners:
|
Mobile App (Licence Code: API05) | This Version 3 public API supports third-party Mobile Apps and the following connections:
Link to GitHub documentation. | Yes Certified Partners:
|
Notifications (Licence Code: API30) | This Version 3 private API allows third-party vendors to generate push notifications within TASS.web and Staff Kiosk and send them to parents via the Parent Orbit app. | No |
Online Enrolments (Licence Code: API04) | This Version 3 public API enables enrolment applications submitted using third-party software to be entered into TASS.web without any manual data entry. Applications entered using this method will be available for processing using TASS.web Student Admin > Enrolments > Enrolment Information > Online Enrolment Applications. Online Enrolment Applications can also be uploaded if the school chooses not to connect via this API. This API allows the school to extract the following details:
Link to GitHub documentation. | Yes Certified Partners:
|
Public Calendar and Notices (Licence Code: API11) | This Version 2 public API allows the school to extract the details and attachments of Daily Notices and Calendar Events flagged for visibility in the Public Calendar. Link to GitHub documentation. | No |
School Calendar and Notices (Licence Code: API19) | This Version 2 public API allows the school to extract the following details:
Link to GitHub documentation. | Yes Certified Partners:
|
Student Academic Analytics (Licence Code: API17) | This Version 2 public API extracts the following information that can be used to generate analytics using third-party software such as Microsoft BI:
Link to GitHub documentation. | No |
Student Details (Licence Code: API12) | This Version 3 public API extracts the following student-related information:
Link to GitHub documentation. | Yes Certified Partners:
|
TASS API Applications Grid
The ‘TASS API Applications Grid’ displays when you select the ‘TASS APIs’ tab. This grid provides an overview of the TASS APIs that are currently enabled for your school.
Grid Column | Description |
|---|---|
App Code | A unique code entered during API setup that the third-party application uses to identify this configuration in API requests. |
Lic. Code | A unique code that is used by TASS to identify the TASS API that is in use. |
Description | The description of the API that was entered during setup. |
App. Server | Details of the originating server for third-party applications. This optional field restricts requests to those from the specified 'Application Server' |
Enabled | This column displays 'Y' if the TASS API is enabled, or 'N' if it is not. |
HTTPS | This field is set to 'Yes' by default, as all portals are required to have 'Secure Socket Layer (SSL)' applied. |
Action | The 'View', 'Edit' and 'Delete' links in the 'Action' column allow you to action existing API Applications. The ‘Log' link allows you to view a list of connections to the API Application. On the 'API Connections Log’ screen, a list of unsuccessful connections can be listed by checking the 'Unsuccessful Connections only' option. You can also use the 'Print' button to generate a report with a list of connections. |
Adding a New TASS API Application
Refer to TASS API Setup Checklist for more information.
If you are integrating with SchoolBox, see SchoolBox Integration Checklist or How to Setup Schoolbox Parent Orbit Notifications.
If you are integrating with TrackOne, see TrackOne Integration Checklist
To add a new TASS API Application, click the ‘Add API Application’ button to display a blank 'TASS API Application Details' screen.
Fields that require further explanation | |
Application Code | Enter a unique code to identify this Application API. This is used by the third-party application to identify this configuration in the API request. |
Application Description | Enter a description for the API configuration. |
Licence Code (Reference) | Select from the picklist provided to choose the API for this configuration. Licence Codes are for categorisation and reference only. Active API licences are not required. |
Application Server | Optional. This is the originating server for third-party applications and is recommended for a live production environment. If an 'Application Server' is entered, requests will only be returned if originating from this server. Use of this setting in conjunction with a proxy server may result in undesired results and/or blocked communication between the two systems. The application server can be a domain, wildcard domain or IP address. Example of usages:
|
Token Key | Click the 'Generate' button to insert a Token. This is a unique token for each TASS API configuration. It is used to secure communication between the TASS server and the third-party system. Modifying this token will block all API communication that utilises a previously generated token. |
HTTPS Only | This field is not editable and will be set to 'Yes'. TASS.web and all portals are required to have 'Secure Socket Layer (SSL)' applied. This will require an SSL Certificate signed by a Certified Authority (CA). |
Enable Photos | The field is only relevant for the following APIs:
When enabled, the student/employee photos in TASS will be transferred and used by the third-party system. |
Enable JSON Logging | Enabling logging will capture the JSON packets resulting from an API request to be stored for auditing and/or debugging purposes. Enabling logging for API requests may increase load on your server and impact disk space. |
Security Role | Optional. This field is only applicable for Version 3 and above APIs. Select from the picklist provided to choose the Security Role to apply the same permissions for this configuration. Security Roles are maintained in TASS.web System Admin > Users > Security Role Permissions. |
Would you like to enable this API? | An API Application can be enabled or disabled using this option. By enabling this API, you are acknowledging that data from the school's TASS database will be transferred to a third-party software system. |