When defining APIs the most common considerations are from what our payload looks like, and then from a implementer perspective.

However, good APIs whether they’re internal or public are far more than just a payload description and need a consumer’s perspective.

In this session we look at what makes up a good API; from OWASP Top 10 implications to ISO and data definitions, to how to make it easy for your consumers, why these points are important and the implications. We’ll explore techniques to overcome of the challenges seen when producing good APIs.

Whilst we all think we know how to define APIs, you’ll be surprised at the things that get overlooked or opportunities to be better.