Bitcoin Price is a simple tool for getting the current price of Bitcoin. It returns the current price, market cap, 24-hour trading volume, and 24-hour price change in any currency.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Bitcoin Price response payload
}
}
About the Bitcoin Price API
Bitcoin Price works by fetching the latest market data for Bitcoin from multiple reliable sources. It returns the current price, market capitalization, 24-hour trading volume, and 24-hour percentage change. The data is refreshed hourly and can be returned in any supported currency.
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
Other ways to use Bitcoin Price
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Bitcoin Price API do?
How do I authenticate Bitcoin Price API requests?
How much does the Bitcoin Price API cost?
How fast is the Bitcoin Price API?
What response formats does the Bitcoin Price API support?
What HTTP method does the Bitcoin Price API use?
Request parameters — GET /v1/bitcoin
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.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
currencyOptionalPremium | string | USD | The currency to get the price in default USD |
hourlyOptionalPremium | boolean | true | Include hourly price data for the past 24 hours default false |
curl "https://api.apiverve.com/v1/bitcoin?currency=USD&hourly=true" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/bitcoin
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.
{
"status": "ok",
"error": null,
"data": {
"currency": "USD",
"price": 97250.43,
"marketCap": 1928000000000,
"volume24h": 35420000000,
"change24h": -1.52,
"lastUpdated": "2026-02-07T12:00:00.000Z",
"high24h": 98750.21,
"low24h": 96125.88,
"changeDirection": "down",
"formatted": {
"price": "$97,250.43",
"marketCap": "$1.93T",
"volume": "$35.42B",
"priceWords": "ninety-seven thousand two hundred fifty dollars"
}
}
}
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 |
|---|---|---|---|
currency | string | "USD" | Currency code in which price is quoted |
price | number | 97250.43 | Current Bitcoin price in specified currency |
marketCapPremium | number | 1928000000000 | Total market capitalization in specified currency |
volume24hPremium | number | 35420000000 | 24-hour trading volume in specified currency |
change24hPremium | number | -1.52 | Percentage price change over the last 24 hours |
lastUpdated | string | "2026-02-07T12:00:00.000Z" | ISO 8601 timestamp of the last price update |
high24hPremium | number | 98750.21 | Highest price in the last 24 hours |
low24hPremium | number | 96125.88 | Lowest price in the last 24 hours |
changeDirection | string | "down" | Price movement direction: up, down, or unchanged |
formatted | object | {...} | |
pricePremium | string | "$97,250.43" | Formatted price with currency symbol and thousands separator |
marketCapPremium | string | "$1.93T" | Formatted market cap in human-readable units (T, B, M) |
volumePremium | string | "$35.42B" | Formatted 24-hour volume in human-readable units |
priceWordsPremium | string | "ninety-seven thousand two hundred fifty dollars" | Price written out in English words for accessibility |
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 | Bitcoin Price 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.
Call it from cURL — GET /v1/bitcoin
No SDK to install — this is a plain HTTPS call to /v1/bitcoin with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/bitcoin" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/bitcoin
Install the Node.js SDK, then call the Bitcoin Price API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/bitcoinconst res = await fetch("https://api.apiverve.com/v1/bitcoin", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/bitcoin
No SDK to install — this is a plain HTTPS call to /v1/bitcoin with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/bitcoin",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/bitcoin
Install the C# / .NET SDK, then call the Bitcoin Price API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.BitcoinPriceusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/bitcoin");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/bitcoin
No SDK to install — this is a plain HTTPS call to /v1/bitcoin 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/bitcoin", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/bitcoin
No SDK to install — this is a plain HTTPS call to /v1/bitcoin with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/bitcoin");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/bitcoin
No SDK to install — this is a plain HTTPS call to /v1/bitcoin with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/bitcoin")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Bitcoin Price form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Bitcoin Price API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Bitcoin Price API.
Finance
- Balance Sheet
- Benchmark Rate
- BIN Lookup
- Bitcoin Price
- Cash Flow Statement
- Company Lookup
- Cost of Living
- CPI Inflation
- Currency Converter
- Currency Symbols
- Dividends
- Earnings Report
- Ethereum Price
- Exchange Rate
- Financial Ratios
- GDP Data
- Global Stock Market
- Gold Price
- I-Bond Rates
- IFSC Lookup
- Income Statement
- Income Tax Brackets
- Income Tax Calculator
- Inflation Rate
- Insider Trading
- Interest Rate
- Jobs Report
- Loan Calculator
- Minimum Wage
- Mortgage Calculator
- Mortgage Rate
- National Debt
- Palladium Price
- Platinum Price
- Population Data
- Purchasing Power
- Routing Number Lookup
- Sales Tax Calculator
- Sales Tax Lookup
- Sanctions Screening
- SEC Filings
- Silver Price
- Stock Exchange
- Stock Market Open Times
- SWIFT Code Lookup
- Trade Balance
- Treasury Yields
- Unemployment Rate
- VAT Rates
Related articles
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