PBoC LPR (PBOC_LPR_1Y) Rate Change

PBoC LPR (PBOC_LPR_1Y) Rate Change

You need to programmatically detect and react to PBoC LPR changes inside your software. By the end of this article, you will query the PBOC_LPR_1Y symbol from the Interest Rates API, interpret its dates and units correctly, compute spreads and payments off the returned value, and ship production-grade integrations using all seven endpoints with robust error handling and caching.

What the PBOC_LPR_1Y symbol represents and how to read it

PBOC_LPR_1Y is the 1-year Loan Prime Rate published for China. In the Interest Rates API, it is a central bank–category benchmark and is tagged to CNY. The frequency is monthly, so you typically receive one prevailing fixing per month. The rate is expressed in annual percentage terms (for example 3 means 3 percent per annum).

Illustration: PBoC LPR (PBOC_LPR_1Y) Rate Change

Effective dates: the API returns a date string (YYYY-MM-DD) for both the overall response and per-symbol dates. For monthly symbols, “the last day with data within that month is used.” In practice, if a fixing is valid for October 2026, the per-symbol date may be “2026-10-31,” indicating the value that applies to that month.

Typical uses include CNY loan pricing, risk dashboards, and macro analysis where you need to compute spreads to other benchmarks or forecast payment streams. Always treat values as percentages, not decimals: a returned value of 3 means 3% p.a., not 0.03.

Reference: See product details at interestratesapi.com. For endpoint shape and model compatibility, visit the MCP.

Discovering the symbol with /symbols

The catalogue endpoint lets you inspect available identifiers, filter by category, base currency, and (optionally) data provider. For PBOC_LPR_1Y, filter by category=central_bank and base=CNY to enumerate China-focused policy and reference rates.

cURL

curl -s "https://interestratesapi.com/api/v1/latest?api_key=YOUR_API_KEY&symbols=PBOC_LPR_1Y"

JSON response

{
    "success": true,
    "date": "2026-10-31",
    "base": "CNY",
    "rates": {
        "PBOC_LPR_1Y": 3
    },
    "dates": {
        "PBOC_LPR_1Y": "2026-10-31"
    },
    "currencies": {
        "PBOC_LPR_1Y": "CNY"
    },
    "base_filter_note": null
}

Key fields:

  • symbol: use this exact identifier in subsequent requests (for this article: PBOC_LPR_1Y).
  • frequency: monthly for PBOC_LPR_1Y.
  • currency_code: CNY for PBOC_LPR_1Y.

Tip: change the base filter to CNY and category to central_bank to locate PBOC_LPR_1Y in your own calls.

Python (requests)

import requests

resp = requests.get(
"https://interestratesapi.com/api/v1/symbols",
params=dict(category="central_bank", base="CNY", api_key="YOUR_KEY")
)
data = resp.json()
print(data.get("success"), len(data.get("symbols", [])))

JavaScript (fetch)

const url = "https://interestratesapi.com/api/v1/symbols?category=central_bank&base=CNY&api_key=YOUR_KEY";
const response = await fetch(url);
const data = await response.json();
console.log(data.success, data.count);

PHP

<?php
$url = "https://interestratesapi.com/api/v1/symbols?category=central_bank&base=CNY&api_key=YOUR_KEY";
$resp = file_get_contents($url);
$data = json_decode($resp, true);
echo $data["success"] ? "OK" : "ERROR";
?>

Get the latest PBOC_LPR_1Y value

Use /latest for the current reading of PBOC_LPR_1Y. The following sample must be used verbatim; it returns the CNY-based rate as a percentage.

cURL (official sample)

JSON (official sample)

How to read it:

  • rates.PBOC_LPR_1Y is 3, meaning 3% per annum.
  • dates.PBOC_LPR_1Y is 2026-10-31, the effective month’s last day with data.
  • base and currencies confirm the CNY context.

Python (requests)

import requests

r = requests.get(
"https://interestratesapi.com/api/v1/latest",
params=dict(api_key="YOUR_API_KEY", symbols="PBOC_LPR_1Y")
)
j = r.json()
lpr = j["rates"]["PBOC_LPR_1Y"]
lpr_date = j["dates"]["PBOC_LPR_1Y"]
print(f"LPR 1Y: {lpr}% on {lpr_date}")

JavaScript (fetch)

const res = await fetch("https://interestratesapi.com/api/v1/latest?api_key=YOUR_API_KEY&symbols=PBOC_LPR_1Y");
const out = await res.json();
const lpr = out.rates.PBOC_LPR_1Y;
const d = out.dates.PBOC_LPR_1Y;
console.log(`LPR 1Y: ${lpr}% (effective ${d})`);

PHP

<?php
$q = "https://interestratesapi.com/api/v1/latest?api_key=YOUR_API_KEY&symbols=PBOC_LPR_1Y";
$out = json_decode(file_get_contents($q), true);
$lpr = $out["rates"]["PBOC_LPR_1Y"];
$date = $out["dates"]["PBOC_LPR_1Y"];
echo "LPR 1Y: {$lpr}% on {$date}";
?>

Point-in-time value with /historical

When you need the value as of a specific date, use /historical. For monthly series, the API resolves the last day with data in that month.

cURL

JSON response

Notes:

  • For monthly frequency, “2025-06-15” will map to the month’s prevailing rate (the last day with data in June).
  • rates is a symbol-to-value map; currencies shows the per-symbol currency code.

Python (requests)

import requests

resp = requests.get(
"https://interestratesapi.com/api/v1/historical",
params=dict(date="2025-06-15", symbols="PBOC_LPR_1Y", api_key="YOUR_KEY")
)
hist = resp.json()
value = hist["rates"]["PBOC_LPR_1Y"]
print(value)

JavaScript (fetch)

const u = "https://interestratesapi.com/api/v1/historical?date=2025-06-15&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
const r = await fetch(u);
const j = await r.json();
console.log(j.rates.PBOC_LPR_1Y);

PHP

<?php
$u = "https://interestratesapi.com/api/v1/historical?date=2025-06-15&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
$j = json_decode(file_get_contents($u), true);
echo $j["rates"]["PBOC_LPR_1Y"];
?>

Time series with /timeseries

Pull an interval of values for PBOC_LPR_1Y. Even for monthly series, the API can present a daily index with the same monthly rate repeated across business days.

cURL

JSON response

Key fields:

  • rates.PBOC_LPR_1Y is a date-to-value map.
  • frequencies shows the output cadence; for monthly symbols it can still be “daily” as values persist across business days.

Python (requests)

import requests

ts = requests.get(
"https://interestratesapi.com/api/v1/timeseries",
params=dict(start="2025-11-16", end="2026-11-16", symbols="PBOC_LPR_1Y", api_key="YOUR_KEY")
).json()
series = ts["rates"]["PBOC_LPR_1Y"]
dates_sorted = sorted(series.keys())
first_date = dates_sorted[0]
print(first_date, series[first_date])

JavaScript (fetch)

const turl = "https://interestratesapi.com/api/v1/timeseries?start=2025-11-16&end=2026-11-16&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
const tresp = await fetch(turl);
const tjson = await tresp.json();
const map = tjson.rates.PBOC_LPR_1Y;
console.log(Object.entries(map).slice(0, 3));

PHP

<?php
$turl = "https://interestratesapi.com/api/v1/timeseries?start=2025-11-16&end=2026-11-16&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
$tjson = json_decode(file_get_contents($turl), true);
$series = $tjson["rates"]["PBOC_LPR_1Y"];
reset($series);
$firstKey = key($series);
echo $firstKey . " -> " . $series[$firstKey];
?>

Change statistics with /fluctuation

To summarize how PBOC_LPR_1Y changed over a window, /fluctuation returns start and end values, absolute and percent change, and the high/low in the period.

cURL

JSON response

Fields:

  • change and change_pct are derived from end_value - start_value and its percentage form (null if start_value is 0).
  • high and low are extrema across the range.

Python (requests)

import requests

f = requests.get(
"https://interestratesapi.com/api/v1/fluctuation",
params=dict(start="2025-11-16", end="2026-11-16", symbols="PBOC_LPR_1Y", api_key="YOUR_KEY")
).json()
stats = f["rates"]["PBOC_LPR_1Y"]
print(stats["change"], stats["change_pct"])

JavaScript (fetch)

const furl = "https://interestratesapi.com/api/v1/fluctuation?start=2025-11-16&end=2026-11-16&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
const fresp = await fetch(furl);
const fjson = await fresp.json();
console.log(fjson.rates.PBOC_LPR_1Y);

PHP

<?php
$furl = "https://interestratesapi.com/api/v1/fluctuation?start=2025-11-16&end=2026-11-16&symbols=PBOC_LPR_1Y&api_key=YOUR_KEY";
$fjson = json_decode(file_get_contents($furl), true);
$stats = $fjson["rates"]["PBOC_LPR_1Y"];
echo "Δ=" . $stats["change"] . " (" . $stats["change_pct"] . "%)";
?>

Monthly OHLC with /ohlc

The API computes OHLC candlestick aggregates on the fly from the daily series. For a monthly PBOC_LPR_1Y view, use period=monthly. The response helps with charting and compact trend summaries.

cURL

JSON response

Interpretation:

  • period: calendar period string like “YYYY-MM”.
  • open/high/low/close: values in percentage terms.
  • data_points: number of daily observations aggregated for that period.

Python (requests)

import requests

ohlc = requests.get(
"https://interestratesapi.com/api/v1/ohlc",
params=dict(symbols="PBOC_LPR_1Y", period="monthly", start="2025-11-16", end="2026-11-16", api_key="YOUR_KEY")
).json()
rows = ohlc["rates"]["PBOC_LPR_1Y"]
for row in rows:
print(row["period"], row["open"], row["close"])

JavaScript (fetch)

const ourl = "https://interestratesapi.com/api/v1/ohlc?symbols=PBOC_LPR_1Y&period=monthly&start=2025-11-16&end=2026-11-16&api_key=YOUR_KEY";
const oresp = await fetch(ourl);
const ojson = await oresp.json();
console.log(ojson.rates.PBOC_LPR_1Y.map(x => [x.period, x.open, x.close]));

PHP

<?php
$ourl = "https://interestratesapi.com/api/v1/ohlc?symbols=PBOC_LPR_1Y&period=monthly&start=2025-11-16&end=2026-11-16&api_key=YOUR_KEY";
$ojson = json_decode(file_get_contents($ourl), true);
foreach ($ojson["rates"]["PBOC_LPR_1Y"] as $row) {
echo $row["period"] . ": O=" . $row["open"] . " C=" . $row["close"] . PHP_EOL;
}
?>

Compare interest costs with /convert

To compare total interest cost of a simple loan using the latest rate of PBOC_LPR_1Y against another benchmark, use /convert. This endpoint computes total interest and total payment for a notional over a term in months.

cURL

JSON response

Fields to use:

  • from/to.rate: the latest rate for each symbol (percent p.a.).
  • total_interest and total_payment: simple-loan arithmetic on the given amount and term.
  • difference.rate_spread: to.rate minus from.rate, in percentage points.

Python (requests)

import requests

conv = requests.get(
"https://interestratesapi.com/api/v1/convert",
params=dict(from="PBOC_LPR_1Y", to="ECB_MRO", amount=100000, term_months=12, api_key="YOUR_KEY")
).json()
print(conv["difference"]["rate_spread"], conv["difference"]["interest_saved"])

JavaScript (fetch)

const cv = await fetch("https://interestratesapi.com/api/v1/convert?from=PBOC_LPR_1Y&to=ECB_MRO&amount=100000&term_months=12&api_key=YOUR_KEY");
const cj = await cv.json();
console.log(cj.difference.rate_spread, cj.difference.interest_saved);

PHP

<?php
$cv = "https://interestratesapi.com/api/v1/convert?from=PBOC_LPR_1Y&to=ECB_MRO&amount=100000&term_months=12&api_key=YOUR_KEY";
$cj = json_decode(file_get_contents($cv), true);
echo $cj["difference"]["rate_spread"] . " pp";
?>

Practical integration notes: units, dates, business days, and caching

Units and rounding: All rates are percentages per annum. Do not divide by 100 unless your downstream math requires decimal form. For display, include a percent sign and consider rounding to 2 decimals, but keep the raw value for analytics.

Effective dates: Use the per-symbol date from the dates map for the final say on when the value applies. For monthly series such as PBOC_LPR_1Y, load the value as of the month’s last day with data, as demonstrated by “2026-10-31.”

Business days: Even monthly benchmarks appear on daily rows in /timeseries. Expect repeated values for each business day. Non-business days may not appear in daily keys; design charts and joins accordingly.

Caching strategy:

  • Latest: cache the latest PBOC_LPR_1Y for the calendar day; for monthly cadence, you may extend cache until your update window (e.g., end-of-month or scheduled publication day) but always revalidate before critical runs.
  • Historical and time series: cache immutable past months aggressively; invalidate only when your system rolls forward.
  • Honor 429 rate limits: check X-RateLimit-Remaining and X-RateLimit-Reset; on 429, respect Retry-After.

Error handling: Parse the standard error shape { success: false, error: "message" } and, for 404s, look for an optional details field to discover available ranges. For 422, validate date formats (Y-m-d) and symbol strings before sending.

Link resources: interestratesapi.com provides product context, and the MCP page lists model compatibility and interfaces. To obtain your key and begin authenticating with api_key query parameters, use Register.

Computing spreads and loan payments off PBOC_LPR_1Y

Spread computation: A spread between PBOC_LPR_1Y and another rate R_other is simply LPR - R_other, in percentage points. For example, if you load both via /latest or /timeseries, compute difference = rates["PBOC_LPR_1Y"] - rates["SOME_SYMBOL"]. Store spreads as signed values and label units as “pp.”

Monthly payment estimation: For a simple interest loan priced at the latest LPR r% per annum over n months and principal A:

  • Monthly rate r_m = r / 12 (still in percent terms).
  • Total interest (simple) = A × (r/100) × (n/12).
  • Equal monthly payment for simple interest approximation = (A + Total interest) / n.

If you use an amortizing loan formula, convert r% p.a. to a monthly decimal i = (r/100)/12, then payment = A × i / (1 - (1 + i)^(-n)). The API leaves amortization choice to your product; ensure consistency across your portfolio tools.

Production checklists for fintech apps, dashboards, and models

  • Use the /latest endpoint for real-time UI widgets; include the per-symbol date beside the value to clarify month and staleness.
  • Backtest or risk models: pull /timeseries and compute rolling spreads or volatilities; for monthly series, aggregate by period boundaries and avoid weekend gaps.
  • Loan comparison UX: use /convert to display the cost difference versus a policy or interbank alternative with the same notional and term; surface rate_spread prominently.
  • Caching and retries: implement a retry with jitter on transient HTTP errors and honor Retry-After after 429 responses. Log X-RateLimit-* headers for capacity planning.
  • Validation: reject user-entered dates not conforming to YYYY-MM-DD before sending to /historical or /timeseries to avoid 422s.

End-to-end example: building an LPR change banner

Goal: Show a banner “LPR 1Y changed X pp since last month” on your homepage.

  1. Call /latest for PBOC_LPR_1Y; record value v0 and its date d0.
  2. Call /fluctuation with start set to the start of last month and end set to end of current month (or to d0), then read change or change_pct.
  3. Render “LPR 1Y: v0% (effective d0). Change since last month: change pp (change_pct%).”
  4. Cache both responses for the day; invalidate at midnight local time or at your market-close batch.

This gives users an immediate sense of direction and magnitude without requiring them to scan charts.

Security, authentication, and environment setup

All endpoints are GET and require an api_key query parameter. Do not send it in headers. In server-side code, store YOUR_API_KEY in environment configuration and inject it into the query string at runtime. For client-side web apps, consider proxying requests through your backend to avoid exposing credentials.

HTTP status codes to handle:

  • 401: Missing or invalid api_key.
  • 403: Account without active plan.
  • 404: No data matched; check symbol and date range; optionally inspect details.
  • 422: Validation error (symbol or date format).
  • 429: Request quota exhausted; back off per Retry-After.

Always parse success in the JSON. Even with HTTP 200, success can be false to indicate an application-level error.

Business-day behavior and monthly cycles for PBOC_LPR_1Y

PBOC_LPR_1Y is monthly. In /timeseries, you’ll see repeated values across business days—this is expected because the prevailing monthly rate applies until the next fixing. The last day with data inside a month becomes the per-symbol date for /latest and /historical resolution.

When syncing month boundaries, rely on dates.PBOC_LPR_1Y to align accounting periods. If you compute month-over-month change, use /fluctuation across the first and last business days in each month to capture accurate start_value and end_value.

Error examples and diagnostics

If you query a date before the available history or after the latest published month:

  • /historical may return 404 with an optional details field describing available ranges. Adjust the date and retry.
  • /timeseries and /fluctuation may succeed but return empty ranges if both start and end are out of bounds. Validate date windows on the client before firing requests.

For throttling, watch X-RateLimit-Remaining and X-RateLimit-Reset. Respect 429 Retry-After before retrying the same endpoint.

FAQ

Q1: Is PBOC_LPR_1Y returned as a decimal or a percentage?
A: Percentage per annum. For example, 3 means 3% p.a. Convert to a monthly decimal by dividing by 100 and then by 12 if you need amortized payments.

Q2: Which date should I display for the latest LPR?
A: Use the per-symbol date from dates.PBOC_LPR_1Y. For monthly series, this is the last day with data in that month, e.g., “2026-10-31.”

Q3: How often does PBOC_LPR_1Y update?
A: Monthly. In daily series outputs, you’ll see the same value repeated across business days until the next month’s fixing.

Q4: Can I compute spreads to other rates?
A: Yes. Pull both symbols via /latest or /timeseries and subtract the values to get a spread in percentage points. The /convert endpoint also returns rate_spread for a notional comparison.

Q5: What happens if I query an invalid symbol or wrong date format?
A: The API returns success=false with 422 Validation error. Ensure symbols are from the documented list and dates use YYYY-MM-DD.

Ship your PBOC_LPR_1Y integration now: fetch current and historical values, compute spreads and payments, and power dashboards and risk engines with clean REST calls. Start with the docs on the MCP page, then get your key at Register and build against interestratesapi.com today.

Ready to get started?

Get your API key and start validating bank data in minutes.

Get API Key