# 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 %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stoobly.com/core-concepts/mock-api/fixtures.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.