Web API Tutorials
Integrating your IRB system to the IRB Exchange using HTTP is the most involved and technically challenging of the integration options. However, it provides the most flexibility. You can choose the programming language of your choice to tailor your integration solution to meet the needs of your own IRB system.
If you are already using Huron Portal, or if your IRB system is built using .NET, we highly recommend using one of the simpler options for integration:
To be successful at building a custom HTTP integration for the IRB Exchange, you must have some familiarity with HTTP and cryptography. These are both heavily used by client applications that use the IRB Exchange for communication, authentication, and data encryption and decryption.
Communication
All communication with the IRB Exchange is done using HTTPS. For more detailed information about communicating with the IRB Exchange, see the Web API Overview. All functionality provided by the IRB Exchange is exposed as an HTTP endpoint. For more details, see Endpoints.
Authentication
Every request made to the IRB Exchange must be signed using a private key from a registered organization. For more information about how to sign a request, please see the detailed information about request signatures.
Encryption and Decryption
All information that is transmitted to the IRB Exchange should be encrypted to protect any sensitive information that it may contain. The information should be encrypted using one of the supported symmetric key algorithms. When encrypted information is received from the IRB Exchange, it will need to be decrypted before it can be processed by your IRB application.
Working with Organizations
- Retrieving organizations using the Web API
- Retrieving an organization's certificate using the Web API
Working with Containers
- Retrieving containers using the Web API
- Creating a container using the Web API
- Granting access to containers using the Web API
- Revoking access from containers using the Web API