Define criteria for onboarding APIs to the API Management Platform
As the API Program team, we should define the criteria for publishing an API in the API Management Platform (Apigee) so that...
- The API Management Platform and developer portal enables discovery of relevant APIs to the broadest campus audience
- There are not duplicative APIs exposed through the platform that might be confusing to consumers
- We can maintain a functional shared environment in the absence of better delegation and technical controls in Apigee
As MS3 has been conducting interviews with campus stakeholders, we've learned of a few APIs that stakeholders might want onboarded. We should determine what we want to expose through the platform. For example, an API that is exclusively consumed internally (e.g. written by a team to be used only by that team) might not be appropriate to share with campus. As another example, what about APIs that will only be consumed by DoIT like the Billing Service?
AC:
- A set of criteria is documented and agreed upon by the API Program team
- The criteria is validated by the Enterprise Integration team (to make sure we can meet the criteria in light of any technical/process limitations today)
- The criteria is published externally