Financial Datasets — Get historical stock price data

Retrieve end-of-day (EOD) historical price data for stocks with the Financial Datasets API. Supply a ticker and an interval. Sample fields include prices and volumes. Build a market research view or track changes over time. The GET request schema also lists start_date.

Selected price
$0.02 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
The stock ticker symbol (e.g. AAPL, MSFT).
The time interval for the price data.
The start date for the price data (format: YYYY-MM-DD).
The end date for the price data (format: YYYY-MM-DD).
Optional parameters (1)
Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.

Sample response

{
  "prices": [
    {
      "close": 243.36,
      "high": 244.15,
      "low": 241.91,
      "open": 243.85,
      "ticker": "AAPL",
      "time": "2025-01-02",
      "volume": 40230800
    },
    {
      "close": 245,
      "high": 245.55,
      "low": 242.8,
      "open": 243.36,
      "ticker": "AAPL",
      "time": "2025-01-03",
      "volume": 38420500
    }
  ]
}

Response result

Response structure

Inferred from examples
  • pricesobject[]
    • closenumber
    • highnumber
    • lownumber
    • opennumber
    • tickerstring
    • timestring
    • volumeinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Financial Datasets — Get historical stock price data with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.