Make the case.
Inspect the outcome.
Choose a fixture, edit its sample input and evaluate it locally. Explore a collection request, a validation error, a schema comparison or a review checklist.
/catalogPagination and empty result
content-type: application/json x-example-mode: offline cache-control: no-store
Evaluation uses bundled rules and synthetic data. Results illustrate a contract; they do not come from a remote API. Reset restores the selected fixture.
Read the fixture reference ↗A few useful answers
Does a fixture need a live API?
A fixture can document an interface independently. Executing it requires a suitable endpoint and separately supplied credentials.
Should response checks match every field?
Check the contract, not incidental formatting. Allow documented optional fields and generated values while validating the parts consumers rely on.
Can production records be used as examples?
Synthetic examples are preferable. Remove secrets and personal information before any request or response is shared.
What belongs in a minimal fixture set?
One normal request, a meaningful empty case, invalid input and a boundary case for the operation. Expand it when a real regression reveals a gap.