Schools increasingly work with flexible and personal learning environments. These are composed of various applications from inside and outside the educational institution. Because these software applications have APIs, it is possible to have them work together. An integration infrastructure allows for the exchange of data between the APIs of these individual applications. This makes the integration infrastructure an indispensable part and you can, for example via apps, make useful information available: from education to credits and from timetables to free workplaces.
Process / Integration facility
Many (higher) educational institutions participate in a standard API: Open Education API. An API is a set of definitions that allow software programs to communicate with each other. It serves as an interface between different software applications. Educational institutions provide useful information through this API: from grades to credits, from timetables to free workplaces. Developers then integrate this data into new applications.
Think of mobile apps where you as a student have easy access to grades, credits, timetables and free workplaces. But also: quickly check in which room a free computer is located, or simply register for an exam.
Not all educational data can be publicly accessible. To secure personal data, such as numbers and timetables, it is recommended to use an authorization server (according to the OAuth 2.0 protocol) in combination with, for example, SURFconext or 1Password. These parts are not part of the OOAPI specification, but are supported.
In addition to all the information that must be available to students, schools have to deal with many other data flows, such as accounting, suppliers, personnel administration, housing, etc.