Vivian Chandra outlines the benefits of an API they created including how it has helped them automate part of their CRM process and protected them from changes of the CRM system.
Simon Ferguson describes how MBIE is using APIs, initiatives that are underway to increase use of APIs, and the considerations that are involved with providing governmental services as APIs.
Owen Rubel talks about IO state that can be shared, cached, synced and reloaded on the fly for all architectural instances without having to restart any instance.
Marc Danneels tells a story on how ASB started using APIs and the lessons learned along the way, covering ASB’s plans to continue extending the API environment externally.
Joe Brophy discusses the journey of NZ Posts digital team from inception to maturity, the new way of working that has developed, combining Design Thinking and Lean Start-up and the role of APIs.
Jason Harmon discusses using API specification formats to drive the development process, focusing on parallelizing work, improving feedback loops, and delivering high quality API products.
Adam Duvander shares 4 API lessons: outsourcing development, possible regrets on making an API public, not all need your API, and an API can provide more opportunities that one can build.
David Harrison presents the API and culture journey at freelancer.com.
Lyndsey Padget introduces the basic principles of RESTful APIs, terminology, design patterns, data, pitfalls, best practices, and others.
Paul Glavich discusses design decisions to be made when building a new API regarding versioning, hypermedia usage, authentication and other aspects.
Mike Amundsen describes a methodology for designing Web APIs (based on the book "RESTful Web APIs") that allows to map key aspects of a business into a usable, scalable, and flexible interface.
Troy Hunt explain how to discover the vulnerabilities of one’s own APIs, identifying common security anti-patterns.