Getting connected
This page outlines how student management system (SMS) suppliers can connect their systems to STARS, for the purposes of testing as well as reporting VET IS data in production. These details apply to both commercial SMS suppliers and in-house registered training organisation (RTO) systems planning to integrate with the STARS APIs.
Getting connected to STARS involves three key steps:
Connect to STARS Client Integration Environment
Test your readiness to connect to production
Onboard registered training organisations to STARS Production Environment
There are two STARS environments available for integration:
STARS Client Integration Environment: test environment that allows SMS operators to test API integrations
STARS Production Environment: live environment used by RTOs to submit reportable data to STARS. The VDS program intends to support SMS suppliers to confirm accurate API integration before onboarding any RTOs to production.
Connecting to the STARS Client Integration Environment (sandbox)
The STARS Client Integration Environment is a test environment that allows SMS suppliers to test their API integrations. Data submitted or actions taken via the Client Integration Environment APIs do not form part of meeting an RTO’s obligations to report data under the Data Provision Requirements (DPRs).
This environment is a non-production sandbox intended for development and testing only. SMS suppliers must not submit real student data or any sensitive information, and should use synthetic or de-identified data when interacting with APIs and workflows.
To connect to the STARS Client Integration Environment, SMS suppliers will need to set up machine-to-machine (M2M) credentials. Use the link below to request to set up organisation/product credentials:
This will create a myVETData Portal account which you will need to use you set up your M2M credentials.
Follow these instructions to create your M2M Credentials or to upload a replacement certificate:
Program and subject data for STARS Client Integration Environment
For testing purposes, an SMS supplier connected to the STARS Client Integration Environment will simulate an RTO to submit training activity data. To submit valid activity data, SMS suppliers will need to use a pre-configured scope of programs and subjects that have been set up to enable effective testing.
SMS readiness to connect
All SMS suppliers must confirm capable integration with the STARS APIs before they begin onboarding RTOs to their system. To support SMS suppliers in their development, the VDS program has outlined a baseline view of what an SMS should be capable of completing via the STARS APIs to be ready to connect to production.
This view allows SMS suppliers (including training organisations with in‑house systems) to validate their API development from a minimally functional perspective – it only outlines the minimum technical API integration requirements and does not include any recommendations on system design or user experience. The STARS APIs have been designed to support a wider set of capabilities and benefits for RTOs and the broader VET sector. SMS suppliers are encouraged to review all information published on the VDS Developer Portal for a comprehensive overview of the intended STARS API design and best practices.
If you are an SMS supplier who provides multiple different products, you are encouraged to assess functionality of each product.
A minimally functional SMS product is able to:
Establish an authenticated connection to STARS
Maintain auditable user authentication
Submit valid reportable data
Reconcile data by reporting period
Remove STARS data reported in error
Check the quality of reported data
Submit end-of-quarter declarations
Connecting RTOs to STARS Production Environment
The STARS Production Environment is the live environment used by RTOs to submit reportable VET IS activity data to STARS.
To connect to the production environment, each ready training organisation will need to request M2M credentials for their organisation. This functionality will be made available via the MyVET Data Portal through the NCVER website in an upcoming release. Training organisations will then configure these credentials in their SMS instance. SMS suppliers may support their customers during this process, however credentials always remain the responsibility of the training organisation.
Training organisations must only use their credentials in an SMS that has confirmed its capable of API integration with STARS. The details for confirming SMS readiness are still being refined, but to support SMS suppliers to commence API development, the VDS program has outlined initial SMS readiness use cases to test against.
M2M credentials for production should only be created once both the SMS and training organisation are ready to transition to report under the VET IS.