PREVIEW · Proposed endpoints and dated plan snapshot · Not ready for public launch
navquote.
Menu
Built for your next integration

Market data.
Ready for
what you build.

Build with stock, crypto, forex and fund data. Add historical candles, streaming updates and market research tools through one API integration.

Continue to our shared account console.

QUOTE / REST
ILLUSTRATIVE RESPONSE · EXCERPT
Repository sample · not liveJSON
FOUR WAYS TO WORK WITH DATA REST requests WebSocket streams Server-Sent Events MCP tools
Financial data, by asset

More than a price.
A market to build around.

Explore data by asset

Asset families in the documented search and data interfaces. Available fields, history and streaming depend on the instrument and plan.

Markets & exchanges

Start with the market
your users follow.

Explore countries, regions and exchange identifiers in the market directory.

Also explore China, India, Latin America, the Middle East and Africa.Browse the market directory

Representative directory entries, not a guarantee of exchange-wide data or real-time feeds.

Build something your users can use

From data access to a working product.

Choose the experience you want to deliver. Follow a concrete path from the first response to the access your application needs.

01 / Your workflow, your interface

From a single quote
to your next application.

Choose the data you need, then choose how your application receives it.

01 / QUOTES

One symbol.
Or a watchlist.

Read a single quote or batch up to 10 symbols. Choose the returned fields and inspect price, timestamp, currency and session.

Explore quotes
02 / HISTORY

Give your charts
some history.

Choose from 1-minute to monthly candles. Set a candle count, a time anchor, and split or dividend adjustment.

Explore historical data
03 / STREAMING

Keep your
interface moving.

Mint a streaming token, subscribe to symbols, and distinguish connection messages from actual quote updates.

Choose your interface
04 / MCP

Put data within
your agent’s reach.

Authorize a compatible AI client, discover its data tools, and return quotes or candle results with timestamps.

Explore MCP
From data to interface

Your data.
Your presentation.

Turn a quote response into a readable watchlist. Keep the source currency and market time alongside the price.

JSON response Your interface
Explore a dashboard workflow
A response, made usefulTwo symbols. A readable watchlist.Archived OpenAPI example · not live prices
InstrumentPriceChange
BINANCE:BTCUSDTUSDT76,513.71+0.89%
BINANCE:ETHUSDTUSDT2,328.83+0.65%

Market timestamp: . Values are retained from the documented batch response, not fetched by this page.

02 / A straightforward start

Your first request.
Then your own workflow.

Use one shared account for API keys, usage and subscriptions. Evaluate the data your product needs, then select the access and request budget that support its day-to-day use.

Preview: neutral endpoints are pending validation. Use the quickstart to review the integration workflow.

Find your integration guide
  1. 01
    Create your account

    Open the shared console and choose a suitable plan.

  2. 02
    Get an API key

    Keep the key in a server-side environment variable.

  3. 03
    Make a request. Inspect the result.

    Check the success field and data timestamp before using the quote.

03 / Beyond the request

A connection that fits.

Compare plan access

REST for snapshots

Choose REST for scheduled reports, exports and a first snapshot. A small field list limits what your app must parse. Batch requests reduce connection overhead, but quota accounting still follows your plan.

Streams for updates

Choose WebSocket when the client sends subscription messages. Choose SSE for server-to-browser events. Both need token-expiry handling and a plan for recovering state after interruptions.

MCP for AI tools

Choose MCP when an agent needs to discover and call data tools. Its session stream is separate from market streaming. Inspect the tool result before asking the model to summarize it.

Beyond the price

Give each number context.

The documented API also includes discovery and research endpoints. Use them to explain what an instrument is and why it belongs in your application.

Find & screen

Resolve a name, ticker, ISIN or CUSIP. Filter the symbol catalog by exchange and primary listing, or run stock scans with discovered filter fields and sorting.

Explore discovery & screening

Research an instrument

Add company identity and annual financials. Use dedicated ETF and options endpoints for holdings or contract discovery instead of expecting them inside a quote.

Explore research endpoints

Follow events

Filter news by symbol or market. Retrieve earnings and economic calendars using Unix-second windows of up to 40 days per request.

Explore news & calendars

Based on the local API v2.4.0 specification. Neutral-domain access and instrument-level availability remain subject to validation.

04 / Know your data

The details matter.
We make room for them.

symbol + currency_code
Identify the listing and currency before reading its price.
lp_time + current_session
Show when the market value was observed, not just when you fetched it.
data.data
Read the nested quote fields. Keep missing values distinct from zero.
Resolve symbols and check availability
From the developer guides

Make the next step concrete.

Browse all guides
Quotes

Get stock quotes in Python

Build a Python quote request with environment credentials, timeout handling, nested response validation and UTC timestamps before storing market data.

Historical data

Export historical OHLCV to CSV with Python

Fetch standard candles, map max and min to high and low, sort and deduplicate timestamps, and export a reproducible CSV with a separate request manifest.

Streaming

REST vs WebSocket vs SSE for market data

Choose a market data transport by interaction pattern, recovery requirements and credential handling, with examples for reports, watchlists and dashboards.

Before your first request

Answers that help
you start building.

Compare access by workload, then use the API reference when you are ready to connect.

Which API should power a watchlist?

Start with batch quotes for up to 10 symbols per request. Read per-symbol success and timestamps. Add WebSocket or SSE when your interface needs pushed updates; keep a snapshot path for reconnection recovery.

Can I choose the fields returned by a quote?

Yes. The contract supports all, price, enhanced, or a comma-separated field list. Request only the fields your screen needs, and handle unavailable values explicitly. Option chains and ETF holdings use dedicated endpoints.

How do I get standard historical candles?

Use /api/price/ohlcv/{symbol}. Choose one of nine documented intervals, a candle count, and a split or dividend adjustment. Use from to fetch forward or to to look backward; from takes precedence if both are present.

Can I use the API from a browser or an AI client?

Keep the long-lived account API key on your server. Mint a short-lived streaming JWT for a browser stream. Hosted MCP uses its own authorization or MCP JWT. The quickstart and connection guides explain each credential path.

Build a first result. Choose the access to grow.

Create your API key in the shared Console, validate your use case, then select a subscription for the features and volume you need.

Get API Key

Continue to our shared account console.