API Contract Court: Break, Version, and Fix a Public API

One team owns an API, another team owns client integrations, and the judge is a failing test suite. Participants introduce versioning mistakes, ambiguous fields, undocumented defaults, and breaking response changes, then negotiate a safer contract.

The lab covers OpenAPI-style thinking, compatibility tests, deprecation notices, error shape design, and migration windows. It is memorable because every bad API decision immediately creates pain for another team in the room.