More talks in the program:
17:30 - 18:20
When defining our APIs, we typically look at things from the inside, understanding how our solution works, and then often think more about the functional consideration – what our payload looks like etc. However, good APIs, regardless of whether they’re internal or public facing, are far more than just a payload description and described from the provider’s perspective.
For a good API, we need to consider many more factors: how we communicate, and even what an API is. In this session we will look at what makes up a good API; from OWASP Top 10 implications to ISO and data definitions, why these points are important, and their implications. We’ll explore techniques to overcome the challenges seen in producing good APIs.
Whilst we all think we know how to define APIs, you’ll be surprised about the things that get overlooked or opportunities to do better.