Beyond the happy path
A real API reference documents every outcome an endpoint can return, not just the success case — every error code, every status value, and what each one means for how the client should respond.
Request and response examples that match reality
Examples that reflect the real shape of requests and responses — not simplified or hypothetical versions — are what let a developer integrate without guessing at details the documentation glossed over.
Operational details developers actually need
Rate limits, idempotency behavior, and authentication requirements per endpoint are operational details that belong in the reference itself, not scattered across separate guides a developer has to find on their own.