In this presentation, I will share how our team created a Person API to improve data integrations with core identity data. Using a technique called contract-first API development, our team was able to show what the API would look like from a user perspective first, which then influenced the technical implementation “under the hood”. I’ll also cover why we chose to create an API, and the benefits behind using APIs for data integrations.
Attendees should have a basic awareness or understanding of APIs would be preferred, but isn’t required. I plan to briefly define an API as a basis for the presentation.
Attendees will learn
– Knowledge of what an API is, and why someone would consume or create one.
– Understanding of APIs compared to how most integrations are implemented at UW-Madison, and why one might prefer an API approach.
– Basic knowledge of API design, and applying UX design techniques when creating a specification for an API to make sure it addresses user needs.
– Understanding of what the Person API is, and a basic understanding of how to get access and use it.
Image by dawnydawny from Pixabay.