Financial Ratios API
Overview
To use Financial Ratios, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/financialratiosExample
How to call the Financial Ratios API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/financialratios?ticker=AAPL&year=2025&quarter=4" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/financialratios?ticker=AAPL&year=2025&quarter=4', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/financialratios?ticker=AAPL&year=2025&quarter=4', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/financialratios?ticker=AAPL&year=2025&quarter=4", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"ticker": "AAPL",
"company": "Apple Inc.",
"cik": "0000320193",
"fiscalYear": 2025,
"fiscalQuarter": 4,
"filingType": "10-K",
"filingDate": "2025-10-31",
"periodEnd": "2025-09-27",
"profitability": {
"grossMargin": 46.91,
"operatingMargin": 31.97,
"netMargin": 26.92,
"returnOnEquity": 151.91,
"returnOnAssets": 31.18
},
"liquidity": {
"currentRatio": 0.89,
"quickRatio": 0.86,
"cashRatio": 0.22
},
"leverage": {
"debtToEquity": 3.87,
"debtToAssets": 0.79,
"equityMultiplier": 4.87,
"interestCoverage": null
},
"efficiency": {
"assetTurnover": 1.16,
"inventoryTurnover": 38.64,
"receivablesTurnover": 10.46
},
"cashFlow": {
"freeCashFlow": 98767000000,
"fcfMargin": 23.73,
"operatingCashFlowMargin": 26.79,
"capexToRevenue": 3.06
},
"perShare": {
"eps": 7.46,
"bookValuePerShare": 4.914,
"freeCashFlowPerShare": 6.5824
}
}
}Authentication
The Financial Ratios API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Financial Ratios API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Financial Ratios API:
Get Financial Ratios by Ticker
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
ticker | string | required | Stock ticker symbol (e.g. AAPL, MSFT, ADBE) Length: 1 - 6 chars | - | |
yearPremium | integer | optional | Fiscal year to retrieve. Defaults to latest available. Range: 2000 - 2030 | - | |
quarterPremium | integer | optional | Fiscal quarter to retrieve. Defaults to latest available. Range: 1 - 4 | - |
Response
The Financial Ratios API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<ticker>AAPL</ticker>
<company>Apple Inc.</company>
<cik>0000320193</cik>
<fiscalYear>2025</fiscalYear>
<fiscalQuarter>4</fiscalQuarter>
<filingType>10-K</filingType>
<filingDate>2025-10-31</filingDate>
<periodEnd>2025-09-27</periodEnd>
<profitability>
<grossMargin>46.91</grossMargin>
<operatingMargin>31.97</operatingMargin>
<netMargin>26.92</netMargin>
<returnOnEquity>151.91</returnOnEquity>
<returnOnAssets>31.18</returnOnAssets>
</profitability>
<liquidity>
<currentRatio>0.89</currentRatio>
<quickRatio>0.86</quickRatio>
<cashRatio>0.22</cashRatio>
</liquidity>
<leverage>
<debtToEquity>3.87</debtToEquity>
<debtToAssets>0.79</debtToAssets>
<equityMultiplier>4.87</equityMultiplier>
<interestCoverage xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</leverage>
<efficiency>
<assetTurnover>1.16</assetTurnover>
<inventoryTurnover>38.64</inventoryTurnover>
<receivablesTurnover>10.46</receivablesTurnover>
</efficiency>
<cashFlow>
<freeCashFlow>98767000000</freeCashFlow>
<fcfMargin>23.73</fcfMargin>
<operatingCashFlowMargin>26.79</operatingCashFlowMargin>
<capexToRevenue>3.06</capexToRevenue>
</cashFlow>
<perShare>
<eps>7.46</eps>
<bookValuePerShare>4.914</bookValuePerShare>
<freeCashFlowPerShare>6.5824</freeCashFlowPerShare>
</perShare>
</data>
</response>
status: ok
error: null
data:
ticker: AAPL
company: Apple Inc.
cik: '0000320193'
fiscalYear: 2025
fiscalQuarter: 4
filingType: 10-K
filingDate: '2025-10-31'
periodEnd: '2025-09-27'
profitability:
grossMargin: 46.91
operatingMargin: 31.97
netMargin: 26.92
returnOnEquity: 151.91
returnOnAssets: 31.18
liquidity:
currentRatio: 0.89
quickRatio: 0.86
cashRatio: 0.22
leverage:
debtToEquity: 3.87
debtToAssets: 0.79
equityMultiplier: 4.87
interestCoverage: null
efficiency:
assetTurnover: 1.16
inventoryTurnover: 38.64
receivablesTurnover: 10.46
cashFlow:
freeCashFlow: 98767000000
fcfMargin: 23.73
operatingCashFlowMargin: 26.79
capexToRevenue: 3.06
perShare:
eps: 7.46
bookValuePerShare: 4.914
freeCashFlowPerShare: 6.5824
| key | value |
|---|---|
| ticker | AAPL |
| company | Apple Inc. |
| cik | 0000320193 |
| fiscalYear | 2025 |
| fiscalQuarter | 4 |
| filingType | 10-K |
| filingDate | 2025-10-31 |
| periodEnd | 2025-09-27 |
| profitability | {grossMargin:46.91,operatingMargin:31.97,netMargin:26.92,returnOnEquity:151.91,returnOnAssets:31.18} |
| liquidity | {currentRatio:0.89,quickRatio:0.86,cashRatio:0.22} |
| leverage | {debtToEquity:3.87,debtToAssets:0.79,equityMultiplier:4.87,interestCoverage:null} |
| efficiency | {assetTurnover:1.16,inventoryTurnover:38.64,receivablesTurnover:10.46} |
| cashFlow | {freeCashFlow:98767000000,fcfMargin:23.73,operatingCashFlowMargin:26.79,capexToRevenue:3.06} |
| perShare | {eps:7.46,bookValuePerShare:4.914,freeCashFlowPerShare:6.5824} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
ticker | string | Stock ticker symbol for the company | |
company | string | Official registered name of the company | |
cik | string | SEC Central Index Key unique identifier | |
fiscalYear | number | Fiscal year of the reporting period | |
fiscalQuarter | number | Fiscal quarter number (1-4) | |
filingTypePremium | string | SEC filing type (10-Q, 10-K) | |
filingDate | string | Date the SEC filing was submitted | |
periodEnd | string | End date of the reporting period | |
profitability | object | - | |
└ grossMargin | number | Gross profit as a percentage of revenue | |
└ operatingMargin | number | Operating income as a percentage of revenue | |
└ netMarginPremium | number | Net income as a percentage of revenue | |
└ returnOnEquityPremium | number | Net income as a percentage of shareholders' equity | |
└ returnOnAssetsPremium | number | Net income as a percentage of total assets | |
liquidity | object | - | |
└ currentRatio | number | Current assets divided by current liabilities | |
└ quickRatioPremium | number | Current assets less inventory over current liabilities | |
└ cashRatioPremium | number | Cash over current liabilities | |
leverage | object | - | |
└ debtToEquity | number | Total liabilities over shareholders' equity |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Financial Ratios through GraphQL to combine it with other API calls in a single request. Query only the financial ratios data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
financialratios(
input: {
ticker: "AAPL"
year: 2025
quarter: 4
}
) {
ticker
company
cik
fiscalYear
fiscalQuarter
filingType
filingDate
periodEnd
profitability {
grossMargin
operatingMargin
netMargin
returnOnEquity
returnOnAssets
}
liquidity {
currentRatio
quickRatio
cashRatio
}
leverage {
debtToEquity
debtToAssets
equityMultiplier
interestCoverage
}
efficiency {
assetTurnover
inventoryTurnover
receivablesTurnover
}
cashFlow {
freeCashFlow
fcfMargin
operatingCashFlowMargin
capexToRevenue
}
perShare {
eps
bookValuePerShare
freeCashFlowPerShare
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Financial Ratios API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Financial Ratios requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Financial Ratios API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Financial Ratios
Official Financial Ratios packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Financial Ratios works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Financial Ratios?
How many credits does Financial Ratios cost?
Each successful Financial Ratios API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful financial ratios lookups.
Can I use Financial Ratios in production?
The free plan is for testing and development only. For production use of Financial Ratios, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Financial Ratios from a browser?
What happens if I exceed my Financial Ratios credit limit?
When you reach your monthly credit limit, Financial Ratios API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








