> For the complete documentation index, see [llms.txt](https://docs.stoobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoobly.com/core-concepts/mock-api/fixtures.md).

# Fixtures

## What are fixtures?

{% hint style="info" %}
Think API intercept and modify behavior in testing libraries
{% endhint %}

Stoobly fixtures are predefined responses used during mocking. Fixtures are used in the case where a recorded response is not found for the current request.

## **Why use fixtures?**

* Quick way to mock a request in the case where a specific response is difficult to record
* Serve assets that otherwise should not be recorded

## Example Fixtures YAML File

The following is an example file for a `fixtures-response.yml` passed to the `--fixtures-response-path` option:

```yaml
DELETE:
    /users/d+?:
        headers: {}
        path: ./relative-path-to-response
        status_code: 200
GET:
    /users/d+?:
        headers: {}
        path: ./relative-path-to-response
        status_code: 200
POST:
    /users:
        headers: {}
        path: ./relative-path-to-response
        status_code: 200
PUT:
    /users/d+?:
        headers: {}
        path: ./relative-path-to-response
        status_code: 200  
```

## Next Steps

{% content-ref url="/pages/GMxOwIvZkyegtOEnzG1D" %}
[How to Use Fixtures](/guides/how-to-mock-apis/how-to-use-fixtures.md)
{% endcontent-ref %}