Overview
Buildmarkets offers two price data endpoints for equities: “a real-time quote endpoint delivering live bid/ask/last data from the market feed, and a historical endpoint returning end-of-day OHLCV bars over any date range.”Real-Time Quotes
Endpoint:GET /v1/marketdata/real-time/{symbol}
Returns live quotes sourced from QuoteMedia, including bid, ask, last trade price, volume, and change data. The service operates “during regular U.S. market hours (9:30 AM – 4:00 PM ET, Monday–Friday, excluding market holidays).”
Path Parameters:
symbol(string, required) – Ticker symbol
symbol,last,bid,ask,bid_size,ask_size,volume,change,change_percent,previous_close,open,high,low,timestamp
Historical Prices
Endpoint:GET /v1/marketdata/historical/{symbol}
Provides end-of-day OHLCV bars spanning multiple years for most U.S.-listed equities.
Path Parameters:
symbol(string, required)
startDate(YYYY-MM-DD, optional) – Defaults to 1 year priorendDate(YYYY-MM-DD, optional) – Defaults to today
date,open,high,low,close,adj_close,volume
adj_close for calculations, as “it accounts for stock splits and dividend distributions, making the series historically consistent.”
Common Errors
Company Profile & Fundamentals
Overview
Buildmarkets provides two key endpoints for accessing company-level financial data. The company profile endpoint delivers “high-level descriptive and valuation data,” while the balance sheet endpoint surfaces “structured financial statements.”Available Endpoints
Two primary routes are offered:GET /v1/marketdata/company-profile/{symbol}— Returns company overview, valuation metrics, and sector classificationGET /v1/marketdata/balance-sheet/{symbol}— Delivers annual or quarterly financial statements
Company Profile Endpoint
This endpoint returns “a rich snapshot of a company — its business description, sector and industry classification, key valuation ratios, market capitalization, and exchange listing information.” Required parameter:symbol (ticker, e.g., AAPL, NVDA)
Key response fields include:
- Company name, description, and exchange listing
- Sector and industry classification
- Market capitalization and valuation ratios (P/E ratio, EPS, dividend yield)
- 52-week price range, average volume, and shares outstanding
- Country, website, CEO name, and employee count
Balance Sheet Endpoint
This endpoint provides “structured financial statements for a symbol — balance sheet, income statement, and cash flow data — in either annual or quarterly form.” Path parameter: Ticker symbol or*CUSIP/*ISIN identifier
Query options:
statementType: Chooseannualorquarterly(default: annual)numberOfReports: Specify number of periods (default: 5)
Common Errors
Possible error responses range from400 INVALID_SYMBOL to 404 SYMBOL_NOT_FOUND and 404 NO_FINANCIAL_DATA.
News, Dividends & Logos
Three companion endpoints round out Buildmarkets’s per-symbol market data surface: news for surfacing relevant articles and corporate actions, cash dividends for historical distribution records, and logos for company brand images. These are especially useful for building rich stock detail pages and notification feeds.Endpoints
News & corporate actions
Returns a list of news articles and corporate action events linked to a specific symbol. Items are returned in reverse chronological order (most recent first). Use thelimit parameter to control how many items you retrieve.
GET /v1/marketdata/news/{symbol}
Path parameters
Query parameters
Response fields
Example request
Example response
Cash dividends
Returns the dividend payment history for a symbol, including ex-dividend dates, record dates, payment dates, and per-share amounts. Supports date range filtering usingexcludingFrom and excludingTo.
Supports lookup by ticker or by CUSIP/ISIN using the * prefix.
GET /v1/marketdata/cash-dividends/{symbol}
Path parameters
Query parameters
Response fields
Example request — last year of dividends
Example response
Logos
Returns the company logo image for a given symbol. The response provides a URL to a hosted image asset suitable for use directly in<img> tags or as a background image.
Logos are provided by QuoteMedia and are updated periodically to reflect rebrands or acquisitions.
GET /v1/marketdata/logos/{symbol}
Path parameters
Response fields
Example request
Example response
Usage tip: Cache logo URLs on your end — they are stable and don’t change frequently. Avoid fetching logos on every page render; retrieve once per symbol and store the URL.
Common errors
Next steps
- Company Profile & Fundamentals → — Add market cap, P/E, and financial statements
- Real-Time & Historical Prices → — Pair news with live price data
- Reference Data → — Browse the full equity universe by sector or symbol list
Reference Data
The Buildmarkets Reference Data endpoints provide programmatic access to the platform’s complete equity universe. These endpoints enable developers to build search features, sector-based screeners, watchlist browsers, and onboarding flows.Available Endpoints
Five primary endpoints serve different discovery needs:- Equity Security Master (
POST /v1/marketdata/reference/equity-security-master) — Returns paginated listings of all tradeable equities with pagination support vialimitandoffsetparameters. - Symbol Details (
POST /v1/marketdata/reference/symbol-details) — Delivers bulk metadata for specific symbols in a single request, useful for watchlist loading. - Sector Symbols (
POST /v1/marketdata/reference/sector-symbols) — Retrieves all tradeable symbols within a designated sector. - List Sectors (
GET /v1/marketdata/reference/sectors) — Provides all recognized sector names as valid inputs for other endpoints. - List Industries (
GET /v1/marketdata/reference/industries) — Returns industry classifications that subdivide sectors for granular filtering.
Key Response Fields
Equity records include symbol, company name, exchange, asset type, CUSIP, ISIN, and tradeable status. The symbol-details response uses a keyed-by-symbol object structure, while list endpoints return arrays.Error Handling
Common HTTP 400 errors includeINVALID_SECTOR (unrecognized sector name), SYMBOLS_REQUIRED (missing symbols array), and TOO_MANY_SYMBOLS (exceeding submission limits).
All endpoints require API key authentication (X-API-Key / X-API-Secret headers, or HTTP Basic auth) and support JSON request bodies to accommodate complex filtering without URL length constraints.