ICON & Third Party Applications

ICON Core Data

The ICON Student Information System (eSIS) is designed to be the single source of truth for each student’s profile and core historical data.

The single source of truth for student profile data will enable efficient integration with other ICON applications eg ePlan, and government or system tools. eg VCAA Insight Assessment.

Because the 'source of truth' for student profile information will be in ICON eSIS, third party applications will be able to access up-to-date student data via the ICON API technology. Student data critical for ePlan will also be able to be brought into ICON where schools use third party applications for this.

ICON Technology Platform - APIs

The ICON eLearn Strategy outlines that the ICON platform will enable schools to continue using selected third party applications that suit their context. The ICON platform will provide Application Programming Interfaces (API) technology which will allow third party applications integration with ICON. Questions about what this means for principals in relation to managing data and vendors is outlined in the ICON and Third Party applications fact sheet.

The first release of ICON (APIs) in July 2020 will enable third party application vendors to access relevant student profile data stored in ICON. This will enable schools to continue using selected third party applications that suit their context. Up-to-date student data will sync to the third party application.

The second release of ICON APIs during the second half of 2020 will provide interfaces to enable student data (attendance, timetable & semester reporting data) from third party applications to be brought back to ICON for use in ePlan.

A benefit for schools using the ICON eLearn Modules for attendance and semester reporting is the effective integration of ICON processes with ePlan. Schools using ICON attendance and semester reporting modules do not have to rely on ICON APIs for this data to be available in ePlan.

Information about ICON APIs for Vendors

Third Party Vendor information for vendors

The above information provides third party application vendors with the steps to begin the process of engaging with ICON and the ICON APIs.

More detailed documentation for vendors can be found by clicking here.

It will be the responsibility of third party vendors to communicate with their schools regarding the status of the development of their product for integration with ICON via APIs.


Vendor API Support Requests

ICON School principals will allow third party applications access to ICON via the ePortal. Principals will agree to terms and conditions regarding the integration of third party applications with ICON. In return the vendors must accept the terms and conditions.

Principals will be required to manage any issues that arise out of the connection with ICON and the third party application directly with their vendor.

ICON will work with vendors to resolve any technical issues .

API contact email: apisupport@cem.edu.au

Frequently Asked Questions

How do I know if a third party application used by the school can integrate with ICON via APIs?

Vendors will communicate with their schools regarding the status of their API development with ICON. If school principals are unsure about this they should contact their third party application vendor.

At this time the SIMON solution is able to access relevant student profile data stored in ICON via the ICON APIs.

What if a vendor does not know about the ICON APIs?

Schools should refer the vendor to this page. Particularly the Information about ICON APIs for Vendors section on this page.

If the school uses a third party application that is not integrated with ICON via the ICON APIs can we export student information from eSIS to upload to the application?

Yes. For those applications that require student information from ICON eSIS there is a method of extracting data for 3rd party vendors directly from eSIS using Crystal reports. Refer to this document.

If our school uses a third party 'Parent Portal' will information updated by parents via this portal pass through to ICON?

ICON will not have APIs available for core student information to flow from third party portals back into ICON eSIS. ICON eSIS must be the 'source of truth' for core information about students. Therefore, core student information must be updated in ICON eSIS by school staff or the school should use the ICON Community Portal for parents to update student information.

Our school is uses a third party application that integrates with ICON via the ICON APIs. There seems to be a problem with the data in the third party application?

Schools must contact their vendor directly if there is an issue. Vendors will engage with ICON if there is a need to resolve technical issues related to APIs.

Key Documents

  • The ICON eLearn Strategy Fact Sheet provides principals with clarity on the eLearn strategy and is critical in helping school leaders make decisions about eLearn technologies going forward.

  • The ICON and Third Party applications fact sheet provides principals with information about managing core data in ICON.

  • The ICON eLearn Modules fact sheet provides information for principals particularly in relation to the attendance and semester reporting modules within ICON. The use of these modules support seamless and efficient integration with ePlan.

  • The ICON Community Portal fact sheet provides principals with information about how the school community can access and update information about their children or students.