Ethereum Price API

About the Ethereum Price API

Ethereum Price works by fetching the latest market data for Ethereum 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.

What people use it for

NFT Mint Quoting

When collectors initiate an NFT purchase, minting engines pull the latest ETH rate to display fiat-equivalent costs before transaction confirmation.

DeFi Collateral Monitoring

Lending protocols evaluate borrower health against liquidation thresholds by verifying real-time price changes and movement direction across active loan positions.

Web3 Paywall Processing

Digital media paywalls compute the exact fractional ETH owed for access passes using real-time price quotes during checkout.

Smart Contract Escrow

To safeguard milestone payouts, freelance escrow platforms record the ETH price and movement direction when an agreement begins.

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

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/ethereum

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

1
2

curl "https://api.apiverve.com/v1/ethereum?currency=USD&hourly=true&hourly[].hour=1&hourly[].price=1&hourly[].timestamp=value" \
  -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.

Response — GET /v1/ethereum

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

{
  "status": "ok",
  "error": null,
  "data": {
    "currency": "USD",
    "price": 2685.12,
    "marketCap": 323000000000,
    "volume24h": 14850000000,
    "change24h": 2.34,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "high24h": 2742.5,
    "low24h": 2618.75,
    "changeDirection": "up",
    "formatted": {
      "price": "$2,685.12",
      "marketCap": "$323.00B",
      "volume": "$14.85B",
      "priceWords": "two thousand six hundred eighty-five 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.

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.

Errors

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

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.

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.

Zero-code embed — one snippet, no backend

Drop an interactive Ethereum 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 — Ethereum 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.

Currently v1Data refreshed realtime