> For the complete documentation index, see [llms.txt](https://docs.blockscholes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockscholes.com/data-access/rest-api/forward-fill.md).

# Forward Fill

Dense minutely series with the forward\_fill request field.

A minutely row is written when a value is observed in that minute. On an illiquid instrument the best bid and ask, or the open interest, can sit unchanged for many minutes, so there is no new row to report for those minutes: the last row still holds. A time-series response returns the rows that were observed, and a consumer who wants a value for every minute has to carry the last one forward themselves.

The optional `forward_fill` request field (default `false`) does that carrying on the server. With `frequency: "1m"` and an explicit `start`/`end` window, the response holds one row per minute: an observed row where there was one, and otherwise a repeat of the last observed row. The field is rejected with HTTP 422 for `LATEST` (which asks for the most recent observed rows and has no grid to fill) and for `frequency: "1h"`. Each endpoint's request table states this where it lists the field.

**Volume is the one exception.** Volume is the sum traded within the minute, not a level that persists between observations. A minute with no row is a minute with no trades, and repeating the previous minute's volume would report trades that did not happen. `/api/v1/analytic/volume` therefore accepts `forward_fill` but returns its rows as observed.

The first bucket is seeded from the last observation found within the lookback, which shares the request's 1-day range budget: a short window leaves most of the day to look back over, a full 1-day window leaves none. If no anchor is found, the leading buckets stay absent, and a window with no observations at all returns 404. When an anchor is found and the window is empty, the whole window is the carried value. The response shape does not change: a carried bucket is an ordinary row with no marker, and signed responses sign carried rows like any other. The field is accepted by every endpoint that takes `frequency`:

| Family             | Endpoints                                                                                                                                      | Note                                                              |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Implied volatility | `/api/v1/iv/strike`, `/api/v1/iv/delta`, `/api/v1/iv/moneyness`, `/api/v1/iv/risk-reversal`, `/api/v1/iv/butterfly-spread`, `/api/v1/iv/index` |                                                                   |
| Model parameters   | `/api/v1/modelparams`                                                                                                                          |                                                                   |
| Prices             | `/api/v1/price/index`, `/api/v1/price/mark`, `/api/v1/price/mid`, `/api/v1/price/trade`, `/api/v1/price/quote`                                 | Quote carries the whole bid/ask row, with sizes, into the bucket. |
| Rates              | `/api/v1/rate/forward`, `/api/v1/rate/funding`                                                                                                 |                                                                   |
| Analytics          | `/api/v1/analytic/oi`, `/api/v1/analytic/volume`                                                                                               | Volume rows are returned as observed, see above.                  |

`/api/v1/price/settlement` and the catalog endpoints do not take `frequency`; settlement accepts and ignores the field, returning the same single value.

**Example** (`POST /api/v1/price/quote`, a Deribit BTC option, five-minute window): the book on this strike was updated at 00:00, 00:01 and 00:04, and sat unchanged in between.

```json
{
    "exchange": "deribit",
    "base_asset": "BTC",
    "quote_asset": "BTC",
    "asset_type": "option",
    "expiry": "2026-12-25T08:00:00Z",
    "strike": [150000],
    "type": ["C"],
    "data_types": ["price", "size"],
    "start": "2026-10-20T00:00:00Z",
    "end": "2026-10-20T00:05:00Z",
    "frequency": "1m",
    "forward_fill": true,
    "options": {
        "format": {
            "timestamp": "s",
            "hexify": false,
            "decimals": 4
        }
    }
}
```

The window is inclusive at both ends, so it has six buckets. Without `forward_fill` the response holds the three observed rows (00:00, 00:01, 00:04). With it, 00:02 and 00:03 repeat the 00:01 row, sizes included, and 00:05 repeats 00:04:

```json
{
    "data": [
        { "timestamp": 1792454400, "bid": 0.0410, "ask": 0.0435, "bid_size": 12.0, "ask_size": 8.5 },
        { "timestamp": 1792454460, "bid": 0.0415, "ask": 0.0435, "bid_size": 10.0, "ask_size": 8.5 },
        { "timestamp": 1792454520, "bid": 0.0415, "ask": 0.0435, "bid_size": 10.0, "ask_size": 8.5 },
        { "timestamp": 1792454580, "bid": 0.0415, "ask": 0.0435, "bid_size": 10.0, "ask_size": 8.5 },
        { "timestamp": 1792454640, "bid": 0.0415, "ask": 0.0440, "bid_size": 10.0, "ask_size": 6.0 },
        { "timestamp": 1792454700, "bid": 0.0415, "ask": 0.0440, "bid_size": 10.0, "ask_size": 6.0 }
    ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blockscholes.com/data-access/rest-api/forward-fill.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
