RS2 API Resources for Developers
The University is moving it's electronic card access solution to RS2's AccessIt! With this change comes support for external integrations via a well-defined RESTful API. For those unfamiliar with the architecture, you can read more general information here on AWS
Access Control will be supporting access to the RS2 API as an extended service to campus developers with a valid need to integrate with the University's access control systems. It is intended that access will be provisioned on a departmental basis rather than individual users. If you have not yet done so, you should request API access by submitting a help request on the Access Control support site . please include the following information:
- Your Department's Active Directory OU Prefix
- Your Cornell NetID
- Source IP addresses, identifying where you will be developing from; we are white-listing access to the API service.
- Existing OnGuard/RS2 segments/sites; your access and permissions will mirror those of your segments.
- Any special considerations you feel we should be aware of.
When your account has been provisioned, you will recieve your username, password, and an API key via the University's Secure File Transfer system. The Access Control Support Team will do its best to support you in the use of the API. Additionally, you will be added to a Lyris mail list intended to encourage community support.
Documentation
The RS2 API is built on the Swagger model which implements the OpenAPI spcification. The RS2 primary end-point can be found by pointing your browser here. The interface is interactive and is a good tool for testing connection strings, filters, etc. The primary documentation can be found at the top of the RS2 end-point page.