PREVIEW · Proposed endpoints and dated plan snapshot · Not ready for public launch
navquote.
Menu
Quote API

A quote for one.
A snapshot for many.

Bring current market quotes into your application. Request a single symbol or a batch of up to 10.

A SMALL REQUEST. USEFUL CONTEXT.

Price is just
the beginning.

Inspect the latest price, available bid and ask, volume, and session context in a structured JSON response.

  • Single quoteGET
  • Batch quotesPOST · up to 10
  • ResponseJSON
Get API Key

Continue to our shared account console.

QUOTE / REST
ILLUSTRATIVE RESPONSE · EXCERPT
Repository sample · not liveJSON
Financial context in your application

Put the instrument around the price.

Explore assets & markets
Stocks

A listing has a session

Keep listed_exchange, currency_code and current_session alongside lp. Add company data through its dedicated endpoint.

Data & availability
Forex

A pair has two sides

Inspect available bid and ask fields with the pair’s source identifier and lp_time. Missing quotes should remain missing.

Data & availability
Crypto

A price belongs to a venue

Keep the full venue-qualified symbol. Check the pair, instrument type and volume units before comparing prices.

Data & availability
Request options

Ask for the fields you need.

Use query parameters for a single quote and JSON properties for a batch. The default session is regular and the default field set is all.

On smaller screens, scroll horizontally to read all columns.

OptionChoose it forImportant detail
fields=priceA compact price-oriented request.Check which timestamp and identity fields your application also needs.
fields=lp,lp_time,currency_codeAn explicit custom field list.Missing or unsupported values still need handling.
fields=allThe standard quote field set.Field availability depends on the instrument and session.
fields=enhancedAdditional instrument-specific scalars.Can include option, bond or ETF attributes; it does not return option chains or ETF holdings.
sessionregular, extended, premarket or postmarket.Requesting a session is not a guarantee that the selected symbol has data for it.

For nested research datasets, use the dedicated options, ETF and company endpoints.

01 / A watchlist in one request

Less polling overhead.
More useful context.

Request multiple symbols together. Inspect each item’s success status so a missing symbol does not hide a usable result.

Batch access and quota accounting depend on your plan. The batch limit is confirmed in source; production behavior still needs verification.

POST/api/quote/batch
REQUEST BODY · EXAMPLE
Check each result, not only the HTTP status.
02 / Read the response

Fields you can work with.

A focused view of common quote fields. Availability varies by instrument.

FieldMeaningIntegration note
lpLatest priceRead alongside the associated timestamp.
lp_timePrice timestampSample uses Unix seconds; verify for your data path.
bid / askAvailable bid and askHandle missing values for unsupported instruments.
ch / chpAbsolute and percentage price change.Preserve the source value and its session context.
currency_codeQuote currency.Do not assume every dollar-denominated display represents USD.
volumeReported volumeUnits and market session depend on the instrument.
current_sessionSession contextDistinguish regular and extended-session data.
Batch response handling

One batch.
Individual outcomes.

A missing symbol does not have to erase a useful row.

  1. Read the envelope

    Check success, then the successful and failed counts.

    Implementation notes

    Inspect data.total, data.successful and data.failed after checking the outer success flag.

  2. Match each symbol

    Handle every item by identity, not array position.

    Implementation notes

    Iterate over data.data. Inspect each item’s success, symbol, data and any error or msg.

  3. Keep a useful state

    Mark failed rows stale or unavailable. Never substitute zero.

    Python watchlist example
    Implementation notes

    Retain the last known state separately from a genuine zero price. Understand the failure before retrying.

03 / Before you connect

A few useful answers.

Are all quotes real-time?

Update behavior depends on the market and instrument. Inspect timestamps and verify coverage for your use case. This preview makes no blanket real-time guarantee.

What happens if one symbol fails?

Batch responses contain per-item results. Check each item’s success status and handle failed symbols separately.

How is a batch request counted?

Quota accounting needs confirmation against the active plan configuration. This design does not assume that ten symbols cost one request.

Can I stream updates instead?

The planned streaming interface supports WebSocket and Server-Sent Events. Access and token limits depend on the plan.

Build something your users can use

See where this API fits.

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

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.

Quotes

Request market data with Node.js fetch

Use native Node.js fetch for server-side market quotes, distinguish HTTP and API failures, and return a small validated response to your frontend.

Start with your first quote.

One account for API keys, usage and subscriptions.

Get API Key

Continue to our shared account console.