In order to access and utilize the web services API, your institution must possess the appropriate product licensing. If you are not sure if your institution has licensed access to the API, please start by contacting a representative from the office, department, or division responsible for purchasing the product. If you are still unsure, contact Engage Support (support@campuslabs.com) and we will be happy to put you in touch with the appropriate representative from our team who can assist you further.

Once you have confirmed you have access to utilize the API, you will need the following:

  1. A web developer or application programmer familiar with the concept of APIs or who is willing to learn
  2. A web server from which to run the code you or your developer/programmer will write to interact with the API (note: depending on what you intend to do with the data you extract from the API, you may also need a database server)
  3. The IP address of the server above
  4. At least one public/private key pair for authenticating your access to the API

Obtaining Access

A key pair consists of a public key (i.e., a special "username" for connecting to the API), and a private key (i.e., a secret value that will be used as a part of your "password" for connecting to the API). Both of these values will be selected for you and for security purposes they will only be given to you or the appropriately-designated individual over the phone. In order to receive a public/private key pair, your institution must first have been verified as owning the appropriate license to use the API. You can have your assigned campus consultant from Campus Labs request a key pair for you, or you can send a request directly to Engage Support (support@campuslabs.com). Requests should include:

  1. Institution name and Engage URL
  2. User's name and their Title or Position
  3. The user's contact email address and a direct office telephone number
  4. IP address of the server from which you will communicate with our API
  5. A brief description of the types of data you intend to access through the API

You will also need to tell us the encryption algorithm to be used for authentication. The supported types include:

  • MD5
  • SHA-256
  • SHA-384
  • SHA-512

Workflow of using the API

Once you have been granted access to the API and have been given a public/private key pair, you may begin writing the code necessary for connecting to and interacting with the API. Your code will generally need to do the following things:

  1. Define any required libraries you may need for creating hash values (these will be used as part of the security/authentication protocol)
  2. Define any required libraries you may need for parsing XML or JSON data
  3. Define any additional libraries you may need for other operations such as database insertions
  4. Set your request header content type to either "text/xml" if you want the API to respond with XML, or "application/json" if you want the API to respond with JSON (if you do not specific a content type on your request, you will receive JSON by default)
  5. Construct a request string (i.e., URL), consisting of:
  6. Make a call to the URL you created above, using the appropriate method for the chosen endpoint
  7. Parse the response from the API, starting with the first page where you will examine the total number of returned pages and items
  8. Create an iterative loop to call each subsequent page and parse its contained data as necessary

Further Information

If you are ready to begin writing your code, please see the documentation on Security and Authentication.

Have more questions? Submit a request