Inflation Rate API GET

Inflation Rate is a tool for retrieving annual inflation rate and CPI data for countries worldwide. It returns the inflation rate, CPI index value, and country details for any year going back to 1960.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/inflation

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Inflation Rate response payload
  }
}

About the Inflation Rate API

Inflation Rate works by aggregating consumer price index data from the World Bank for over 180 countries. It provides both the annual inflation rate (year-over-year percentage change in consumer prices) and the CPI index value (base year 2010 = 100). Data is refreshed daily.

What people use it for

Economic Analysis: Use the Inflation Rate API to analyze inflation trends across countries and time periods for economic research and reporting
Financial Planning: Incorporate inflation data into financial planning tools to adjust projections and account for purchasing power changes
Currency Analysis: Compare inflation rates across countries to understand currency strength and purchasing power parity
Data Visualization: Build dashboards and charts showing historical inflation trends by country using the Inflation Rate API

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Inflation Rate

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Inflation Rate API.

Read the docs →

What does the Inflation Rate API do?

How do I authenticate Inflation Rate API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Inflation Rate API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Inflation Rate API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Inflation Rate API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Inflation Rate API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/inflation

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`country`Required	string	`US`	ISO 2-letter country code (e.g., US, GB, JP, DE, BR) length 2-2

Optional

Parameter	Type	Example	Description
`year`OptionalPremium	integer	`2023`	The year to retrieve data for. Defaults to the previous year. range 1960-2030

Example request

1
2

curl "https://api.apiverve.com/v1/inflation?country=US&year=2023" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/inflation

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "country": "US",
    "countryName": "United States",
    "year": 2023,
    "inflationRate": 4.12,
    "cpiIndex": 139.81,
    "cpiBaseYear": 2010,
    "lastUpdated": "2026-02-05T04:00:00.000Z"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`country`	string	`"US"`	ISO 2-letter country code of the requested country
`countryName`	string	`"United States"`	Full name of the country in English
`year`	number	`2023`	Year for which inflation data was retrieved
`inflationRate`	number	`4.12`	Annual inflation rate as percentage year-over-year change
`cpiIndex`	number	`139.81`	Consumer Price Index value for the year
`cpiBaseYear`	number	`2010`	Base year used for CPI calculation and comparison
`lastUpdated`	string	`"2026-02-05T04:00:00.000Z"`	ISO 8601 timestamp of last data update

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Inflation Rate calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/inflation

No SDK to install — this is a plain HTTPS call to /v1/inflation with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/inflation" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/inflation-apiSource, issues and the examples this page is built from.ReferenceInflation Rate API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/inflationnpm APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/inflation

Install the Node.js SDK, then call the Inflation Rate API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/inflation

Node.js

const res = await fetch("https://api.apiverve.com/v1/inflation", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/inflationThe published Node.js client, versioned and signed.GitHubapiverve/inflation-apiSource, issues and the examples this page is built from.ReferenceInflation Rate API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/inflation

No SDK to install — this is a plain HTTPS call to /v1/inflation with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/inflation",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/inflationnpm APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/inflation

Install the C# / .NET SDK, then call the Inflation Rate API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.InflationRate

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/inflation");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.InflationRateThe published C# / .NET client, versioned and signed.GitHubapiverve/inflation-apiSource, issues and the examples this page is built from.ReferenceInflation Rate API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/inflationnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/inflation

No SDK to install — this is a plain HTTPS call to /v1/inflation with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/inflation", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/inflationnpm APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/inflation

No SDK to install — this is a plain HTTPS call to /v1/inflation with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/inflation");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/inflationnpm APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/inflation

No SDK to install — this is a plain HTTPS call to /v1/inflation with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/inflation")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/inflationnpm APIVerve.API.InflationRateNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Finance

View all 49 →

All articles →

Enrich Your CRM with Public Company DataAutomatically fill in company details for sales leads using SEC data. Ticker, industry, address, and more from a single API call.Read

Currency Conversion: Handling Exchange Rates CorrectlyExchange rates change constantly. Learn how to handle currency conversion in applications with accuracy and reliability.Read

Going Global: Building Multi-Currency AppsYour app works great in dollars. Now a customer in Germany wants to pay in euros. Here's what to know.Read

Inflation Rate API GET

Try it — live request, no key required

About the Inflation Rate API

What people use it for

Ways to call it

Other ways to use Inflation Rate

Questions.

Request parameters — GET /v1/inflation

Required

Optional

Authentication

Response — GET /v1/inflation

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/inflation

Resources

Also published for

Call it from Node.js — GET /v1/inflation

Resources

Also published for

Call it from Python — GET /v1/inflation

Resources

Also published for

Call it from C# / .NET — GET /v1/inflation

Resources

Also published for

Call it from Go — GET /v1/inflation

Resources

Also published for

Call it from PHP — GET /v1/inflation

Resources

Also published for

Call it from Ruby — GET /v1/inflation

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Inflation Rate API

Finance

Related articles

Ready to build with Inflation Rate? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog