---
title: "How do I load interest rate fixings into the Quote Store?"
slug: "how-do-i-load-an-interest-rate-fixing-into-the-lusid-quote-store"
updated: 2026-05-07T11:34:36Z
published: 2026-05-07T11:34:36Z
canonical: "support.lusid.com/how-do-i-load-an-interest-rate-fixing-into-the-lusid-quote-store"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I load interest rate fixings into the Quote Store?

You can load a fixing representing a published benchmark or reference interest rate for a given day, for example 1.24224503 for SOFR on 6 May 2026.

Note the following:

- Interest rate fixings are required items of market data for instruments with floating legs such as certain [complex bonds](/v1/docs/modelling-complex-bonds-in-lusid) and [interest rate swaps](/v1/docs/modelling-interest-rate-swaps-in-lusid), to calculate cashflows and accrued interest.
- Choices you make when uploading market data impact the composition of the [recipe](/v1/docs/what-is-a-recipe) you must create in order to use that data.

**See also**: [Market prices](/v1/docs/how-do-i-upload-a-market-price-or-fx-spot-rate-to-the-quote-store) | [FX spot rates](/v1/docs/how-do-i-load-fx-spot-rates-into-the-quote-store) | [Inflation fixings](/v1/docs/how-do-i-upload-an-inflation-fixing-to-the-lusid-quote-store)

## Methods

LUSID web appLUSID APILuminesce

Call the [UpsertQuotes](https://www.lusid.com/docs/api#operation/UpsertQuotes) API to load up to 2000 quotes in a single request. You must:

- Encapsulate all the quotes in a single `scope` (namespace) in the URL.
- For each quote, specify an ephemeral ID (to track errors in the response).

```json
curl -X POST "https://<your-domain>.lusid.com/api/api/quotes/MyFixings"
  -H "Authorization: Bearer <your-API-access-token>"
  -H "Content-Type: application/json-patch+json"
  -d '{
  "Quote-0001": {
    "quoteId": {
      "quoteSeriesId": {
        "provider": "Lusid",
        "instrumentIdType": "RIC",
        "instrumentId": "GBP-LIBOR",
        "quoteType": "Price",
        "field": "mid"
      },
      "effectiveAt": "2026-01-01T00:00:00Z"
    },
    "metricValue": {
      "value": 0.497534, "unit": "GBP"
    }
  },
  "Quote-0002": {
    "quoteId": {
      "quoteSeriesId": {
        "provider": "Lusid",
        "instrumentIdType": "RIC",
        "instrumentId": "GBP-LIBOR",
        "quoteType": "Index",
        "field": "mid"
      },
      "effectiveAt": "2027-01-01T00:00:00Z"
    },
    "metricValue": {
      "value": 0.512738, "unit": "GBP"
    }
  }
}'
```

Navigate to **Data Management > Quotes** and click the **Create quote** button:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-RQR45Y1W.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A00%3A28Z&se=2026-11-09T07%3A00%3A28Z&sr=c&sp=r&sig=EJqZELfy0pN5F%2BoeS8%2B2RXMFQadMvEI%2FXaL0h5mK%2B0M%3D)

Write a Luminesce SQL query using the [Lusid.Instrument.Quote.Writer](/v1/docs/lusidinstrumentquotewriter) provider and execute it using a tool such as the LUSID web app:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-P32851H9.png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A00%3A28Z&se=2026-11-09T07%3A00%3A28Z&sr=c&sp=r&sig=EJqZELfy0pN5F%2BoeS8%2B2RXMFQadMvEI%2FXaL0h5mK%2B0M%3D)

## Data fields

This section supplements the [API documentation](https://www.lusid.com/docs/api/lusid/endpoints/quotes/UpsertQuotes/) and on-screen help text in the LUSID web app.

| Mandatory field or parameter | Allowed values | Must be matched in recipe? |
| --- | --- | --- |
| `scope` | Any, for example `MyLIBORFixings` | ✅ [dataScope field](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) |
| `provider` | [Any valid](/v1/docs/understanding-valid-market-data-provider-and-field-combinations) | ✅ [supplier field](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) |
| `field` | [Any valid for provider](/v1/docs/understanding-valid-market-data-provider-and-field-combinations) | ✅ [field field](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) |
| `instrumentIdType` | `RIC` or `ClientInternal` | ✅ [key field](/v1/docs/recipes-locating-market-data#more-information-on-the-key-field), for example `Quote.RIC.GBP-LIBOR` or `Quote.ClientInternal.*` |
| `instrumentId` | Must match the `fixingReference` field in the [index convention](/v1/docs/flow-conventions-and-index-conventions) of an instrument such as an IRS, for example `GBP-LIBOR` |
| `quoteType` | `Index` or `Rate` | ✅ [quoteType field](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) |
| `effectiveAt` | A UTC datetime, or date and [cut label](/v1/docs/what-is-a-cut-label) | ❌ [but must be within quoteInterval](/v1/docs/recipes-locating-market-data#more-information-on-the-quoteinterval-field) |
| `metricValue.value` | The actual published rate, for example `0.489734` | ❌ |
| `metricValue.unit` | Any intuitive string, for example `GBP` or `None` | ❌ |

The following fields are optional:

- A `priceSource` indicating a sub-supplier to the `provider`, for example Tradeweb or RRPS for Refinitiv DataScope. [**Match this using the priceSource field in a recipe**](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule). Note that if omitted, your recipe must also omit its `priceSource` field.
- A `lineage` providing additional information.
- We recommend *not* setting a `scaleFactor` for an interest rate fixing.

## Subsequent updates

You can change the `metricValue` of an existing quote. Any other update constitutes a new quote in the time series.