Business Quant API Documentation
Welcome to the official developer portal for the Business Quant API. Access institutional-grade financial statements, granular segment data, SEC filings, insider transactions, and analyst estimates through our high-performance REST infrastructure.
Base URL
All API requests should be directed to the following base URL. Endpoints are accessed exclusively via secure HTTP GET requests, passing your api_key as a URL query parameter.
https://data.businessquant.com
Explore the Endpoints
Select an endpoint below to view its available parameters, authentication requirements, and standard JSON response formats.
Stocks Profile
Retrieve comprehensive metadata, descriptive profiles, and master identifiers (CIK, CUSIP) for publicly traded equities.
Funds Profile
Retrieve metadata, descriptive profiles, and master identifiers specifically tailored for mutual funds and ETFs.
Financial Statements
Extract deeply formatted Income Statements, Balance Sheets, Cash Flows, and calculated financial ratios.
Analyst Estimates
Track forward-looking Wall Street consensus estimates for revenue and EPS across future quarters and years.
Dividends
Get historical dividend payments, ex-dividend dates, and calculated trailing twelve-month (TTM) daily yields.
Segments Data
Extract deeply categorized operating metrics, regional geographic revenues, and product division performance.
Peers Analysis
Dynamically fetch competitors and calculate aggregated sector or industry averages and medians across custom metrics.
SEC Filings
Search, filter, and retrieve exact SEC EDGAR filing URLs, accessions, and publication dates for public companies.
Institutional Ownership
Access detailed records of institutional fund holdings, composition, and quarterly 13F filing aggregates.
Insider Transactions
Track executive and director trading activity. Insider ownership data is sourced comprehensively from SEC Forms 3, 4, and 5.
Standard Response Architecture
To ensure consistency and ease of programmatic integration, every Business Quant API response follows a strict, predictable JSON schema. The output is always divided into two primary objects:
metadata: Contains the contextual parameters of your request. This includes the resolved identifiers (CIK, Tickers), company names, matched modes, and pagination details to help your application process the payload statefully.data: Contains the requested dataset. Depending on the endpoint, this will be formatted as an array of objects (like Peers or Filings) or a nested hierarchical object (like Financial Statements).
{
"metadata": {
"ticker": "AAPL",
"companyname": "Apple Inc.",
"page": 1,
"total_records": 150
// ... contextual variables confirming your query
},
"data": [
// ... the requested dataset array or object
]
}
Error Codes & Handling
The Business Quant API uses conventional HTTP response codes to indicate the success or failure of an API request. Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., missing parameters, invalid API key, or not found). Codes in the 5xx range indicate an issue with our backend servers.
| HTTP Code | Error Title | Description & Resolution |
|---|---|---|
200 |
OK | The request was completely successful and the requested JSON payload is returned. |
400 |
Bad Request | The request was unacceptable. This typically happens if you omitted a required parameter, provided invalid formatting (e.g., a bad date string), or provided conflicting filters. |
401 |
Unauthorized | No valid API key provided. Ensure you are successfully appending your api_key as a URL query parameter to the request. |
403 |
Forbidden | The API key is valid, but your account lacks permissions to access the requested endpoint, or your subscription tier limits access to this specific module. |
404 |
Not Found | The requested resource does not exist. This commonly occurs if you pass an invalid, unknown, or delisted ticker, or an incorrect SEC accession number. |
422 |
Unprocessable Entity | A parameter was passed, but it failed schema validation (e.g., passing a string into an integer-only field like limit or page). |
429 |
Too Many Requests | You have exceeded your account's rate limit or your total monthly API quota. Please slow down your request volume or upgrade your subscription tier. |
500 |
Internal Server Error | An unexpected issue occurred on our backend infrastructure. These errors are logged and monitored actively by our engineering team. |