An API reference needs more than field names. State what an operation changes, which inputs are required and how a client can distinguish a temporary problem from an invalid request.
Describe its purpose.
Show a valid request.
Explain a meaningful failure.
Choose a useful next step.
Explore endpoints, request examples and response behavior in a clear working reference. API Workbench keeps the contract understandable for the people building on either side of an interface.