Code
Build a mock API
A running mock plus a docs portal you can actually click through.
Fill it in
If you have one.
Resources, operations, and the shapes.
Lumpy, with empty states and long values.
Your prompt
Build a mock API and a docs portal. [your or describe the api] Make the mock behave, not just respond. Validate the request the way the real one will, return the real error shapes for bad input, and honour pagination. A mock that returns 200 for everything lets a client ship code that has never handled a failure. Generate realistic data: lumpy distributions, empty results, long names, and at least one record with every optional field missing. Perfect fixtures are why a UI breaks on the first real response. The docs portal has a try-it button wired to the mock, so a reader can send a request without setting anything up. That is the entire reason to build the portal.
Use Build a mock APIOpens with everything above already filled in.
Why this works
A mock that returns 200 for everything lets a client ship code that has never handled a failure. This validates requests, returns the real error shapes, and generates lumpy data with empty states, because perfect fixtures are why a UI breaks on the first real response.