James Seconde

Awful APIs: A History Lesson in Industry Mistakes and Mishaps

What if a GET request could delete customer data? This humorous tour of API history explores the industry's biggest mishaps so you don't repeat them.

Awful APIs: A History Lesson in Industry Mistakes and Mishaps
#1about 5 minutes

Understanding the original concept of an API

An API was originally just a defined interface for one local application to talk to another, illustrated with a simple PHP function.

#2about 4 minutes

Communicating between machines with remote procedure calls

As computers became networked, Remote Procedure Calls (RPC) emerged as a way to execute code on a remote server, with JSON-RPC as a key example.

#3about 3 minutes

The enterprise era of SOAP and its XML complexity

The Simple Object Access Protocol (SOAP) was created for enterprise needs but introduced significant complexity with its verbose XML-based format.

#4about 2 minutes

Simplifying APIs with REST and standard HTTP verbs

Representational State Transfer (REST) simplified API design by leveraging the existing HTTP protocol, using verbs like GET, POST, and DELETE to manage resources.

#5about 5 minutes

The need for standards and common pitfalls of REST

Without clear standards, REST APIs can be implemented incorrectly, leading to security vulnerabilities and unpredictable behavior as seen with HATEOAS and real-world examples.

#6about 1 minute

Formalizing REST APIs with OpenAPI and Swagger

The OpenAPI specification (formerly Swagger) provides a standardized way to define REST APIs, enabling auto-generation of documentation, client code, and tests.

#7about 2 minutes

GraphQL as an alternative to avoid multiple API requests

GraphQL was developed to solve the problem of over-fetching or under-fetching data by allowing clients to request exactly the data they need in a single call.

#8about 2 minutes

History repeating with modern frontend frameworks

Modern tools like HTMX and Laravel Livewire are returning to sending HTML over the wire, echoing older web development patterns and showing the cyclical nature of technology.

#9about 1 minute

The cyclical nature of API design and development

The history of APIs demonstrates a repeating cycle of innovation, standardization, complexity, and simplification, urging developers to learn from the past.

Related jobs
Jobs that call for the skills explored in this talk.

Matching moments

Organizing a developer conference for 15,000 attendees
01:32 MIN

Organizing a developer conference for 15,000 attendees

Cat Herding with Lions and Tigers - Christian Heilmann

Increasing the value of talk recordings post-event
04:57 MIN

Increasing the value of talk recordings post-event

Cat Herding with Lions and Tigers - Christian Heilmann

Selecting strategic partners and essential event tools
03:17 MIN

Selecting strategic partners and essential event tools

Cat Herding with Lions and Tigers - Christian Heilmann

Establishing a single source of truth for all data
02:39 MIN

Establishing a single source of truth for all data

Cat Herding with Lions and Tigers - Christian Heilmann

Why HR struggles with technology implementation and adoption
04:22 MIN

Why HR struggles with technology implementation and adoption

What 2025 Taught Us: A Year-End Special with Hung Lee

Breaking down silos between HR, tech, and business
03:39 MIN

Breaking down silos between HR, tech, and business

What 2025 Taught Us: A Year-End Special with Hung Lee

Automating formal processes risks losing informal human value
03:48 MIN

Automating formal processes risks losing informal human value

What 2025 Taught Us: A Year-End Special with Hung Lee

Rapid-fire thoughts on the future of work
02:44 MIN

Rapid-fire thoughts on the future of work

What 2025 Taught Us: A Year-End Special with Hung Lee

Featured Partners

Related Videos

See all videos
REST in Peace? What does the API protocol of the future look like? Or do we have it already?20:29

REST in Peace? What does the API protocol of the future look like? Or do we have it already?

Simon Auer

API = Some REST and HTTP, right? RIGHT?!27:25

API = Some REST and HTTP, right? RIGHT?!

Rustam Mehmandarov

The year 3000, a brief history of Web Development25:30

The year 3000, a brief history of Web Development

Lorenzo Pieri

Lessons learned from observing a billion API requests23:47

Lessons learned from observing a billion API requests

Pratim Bhosale

Evolving your APIs, a step-by-step approach28:49

Evolving your APIs, a step-by-step approach

Nicolas Fränkel

Lessons from Our API Past: Evolving to a Resilient API Future29:30

Lessons from Our API Past: Evolving to a Resilient API Future

Yousaf Nabi

API Design - Getting Started44:15

API Design - Getting Started

Alen Pokos

The Great API Debate: REST, GraphQL, or gRPC?28:16

The Great API Debate: REST, GraphQL, or gRPC?

Alexis Yushin

Related Articles

View all articles
CH
Chris Heilmann
All the videos of Halfstack London 2024!
Last month was Halfstack London, a conference about the web, JavaScript and half a dozen other things. We were there to deliver a talk, but also to record all the sessions and we're happy to share them with you. It took a bit as we had to wait for th...
All the videos of Halfstack London 2024!

From learning to earning

Jobs that call for the skills explored in this talk.