API Design Starts With the Client Workflow

A good API is not just a list of resources. It is a set of promises made to real consumers: frontend screens, mobile flows, partners, dashboards, and automation workers.

When I design an API, I start by mapping the consumer workflow. What does the client need to know first? Which state changes matter? Which errors can the user recover from? Which fields must be stable for integrations?

That workflow-first approach produces APIs that are easier to use, easier to document, and easier to evolve.