3 good ways to validate APIs

Here’s a situation I am certain many software developers have faced when building or enhancing a new application.

The product owner defines an epic and several features requiring integrations with a new SaaS application. She’s made several assumptions about what capabilities the SaaS platform exposes in their APIs and has baked these into workflow and front-end application requirements. She expects the agile development team to complete a spike, ideally in one sprint, to validate these assumptions.

The question is, how easy is it for the development team to perform this investigation and ideally implement proofs of concept that validate assumptions?

To read this article in full, please click here