Skip to main content

​
Introduction

Buildmarkets’s Market Data APIs offer access to comprehensive financial data for U.S.-listed equities, sourced from QuoteMedia. All data comes included with your Buildmarkets integration—no separate subscription needed.

​
Available Data Categories

The platform provides:
  • Real-time quotes via GET /v1/marketdata/real-time/{symbol} — current bid, ask, last price, and volume
  • Historical prices via GET /v1/marketdata/historical/{symbol} — end-of-day OHLCV bars with date filtering
  • Company profile via GET /v1/marketdata/company-profile/{symbol} — market cap, P/E ratio, sector, description
  • Financials via GET /v1/marketdata/balance-sheet/{symbol} — balance sheets and income statements (annual and quarterly)
  • Dividends via GET /v1/marketdata/cash-dividends/{symbol} — cash dividend records with ex-dates
  • News via GET /v1/marketdata/news/{symbol} — articles and corporate actions linked to symbols
  • Logos via GET /v1/marketdata/logos/{symbol} — company logo images
  • Reference data — security master, symbol details, sectors, and industries

​
Symbol Formats

Endpoints accept ticker symbols (e.g., AAPL) or identifiers with a * prefix:
  • *CUSIP format for CUSIP-based lookups
  • *ISIN format for international securities identification
The asterisk prefix indicates the API should treat input as an instrument identifier rather than a ticker symbol. This feature works on balance-sheet and cash-dividends endpoints.

​
Complete Endpoint List

​
Authentication

All endpoints use API key authentication. Pass your key pair either as request headers:
or as HTTP Basic auth (Authorization: Basic base64(api_key:api_secret)). Refer to the Authentication Overview documentation for additional details.

​
Rate Limiting

Market data endpoints share the same rate limit pool as other Buildmarkets API endpoints. Real-time quote endpoints support frequent polling but shouldn’t exceed one call per second per symbol in production environments. For high-frequency display scenarios, implement client-side caching with a short TTL (1–2 seconds recommended).