UNIC Virtual Campus is envisioned as a central informational hub, which uses a subset of informations that originates from a local partner universities' Student Management Systems (SMSs). That information could be entered manually using a Virtual Campus applications, but the preferred way of doing it, is programatically, using Application Programming Interface (API). This API uses REST paradigm, and a number of end-points are provided in order to be able to enter or pull as much of information as possible to/from Virtual Campus database. 

More information about UNIC REST API and available resources can be found in the swagger documentation: https://unic.srce.hr/swagger/index.html (production system).
Swagger documentation for testing system is available at: https://webtest.unic.srce.hr/swagger/index.html.

In order to provide you the credentials for using this API, we need the data about your organization’s software that will serve as a REST API client (we call it RIS – REST information system), so that they can access and use the REST API. 

Required data about the RIS:

1. RIS Name 
2. RIS Abbreviation 
3. Owner Organization Name (Your institution)

Optional data about the RIS:
1. RIS Description 
2. RIS Info URL 
3. RIS Contact Email 
4. RIS Contact Phone 

This data can be sent to us at: unicvc-support@srce.hr.

After we receive the data and enter it in the central register, the username and a password will be send for organization’s RIS in separate emails. That username and password are mandatory for every API request. API will serve the data only relevant to the university, which is bound to the corresponding RIS, i.e. username. The username and password are different for production and testing systems.

Some API endpoints (i.e. those related to user administration) are additionally secured. In addition to username and password, these endpoints also require an identifier of a real user (a person) who is the one „working" with the system. That user should have an appropriate level of rights in the system (e.g. UNI Admin) in order for these actions to be performed.

  • No labels