API Directory

Overview This document outlines information on the universitywide API Directory.
Overview This document provides information on generating and renewing access tokens.
Overview This document outlines the procedure for adding an user to the existing Provider Organization. Only the users having the role of Administrators and Security Admins can add users to the Provider Org. Pre-requisites Before going into the product and granting the access, ensure the Service Link flow for the Join a Provider Org is completed. Once the API Directory / Service Management team approves the task in the workflow, Access and Accounts will get a task for granting the access.
Overview The API Directory organizes API's by The University of Michigan's Institutional Data Areas. More on the Data Areas can be found here. The info-graph below show's each Data Area and their sub-categories. The Data Areas with bold currently have API's published through the API Directory.    
Overview This document provides field/section descriptions for the API Directory. This field description focuses on fields encountered when creating and testing an API. For steps on how to create and test an API, see Create and Test an API. Field/Section Descriptions
Overview This document contains a glossary with an alphabetical list, definitions, and of terms related to APIs/API Directory. Below the Glossary are some frequently asked questions (FAQ) with the applicable answers.
This document outlines the procedure for creating and testing an API.
This document outlines the procedure for publishing an API.
This document outlines the procedure for subscribing to an API.
Overview This document outlines the procedure for approving a subscription request in the API Manager for the restricted APIs. In the new IBM API Manager, the subscription requests made by any developer organization for a restricted API are sent to the Provider Organization owners, Product Managers and Security Admins.