API Strategy & Practice Conference 2018

In a perfect world, all of the business requirements for an API would be set in stone before the API is built out. But that rarely happens. Perhaps a client changes its requirements midway through the project, or a product manager doesn't yet know all of the features the API must support, or evolving technical requirements necessitate changes to the structure of the API.

Shaun Gallagher, Monetate's Enterprise Integration Architect, will walk through how to design an API when the business requirements are not yet finalized or have changed during the course of the project, and how to improve processes around that API, such as versioning and release notes, to minimize the impact of that API evolution on existing users.