Designing an API is easy. Designing one that survives five years of consumers, growth, and team turnover is hard.

Most APIs don't fail because of bad endpoints. They fail because of small early decisions (a pagination shortcut, a non-idempotent POST, an error format that nobody can parse) that compound into integration nightmares.

This lesson covers the patterns senior engineers reach for, and the traps they avoid.