Growth
Retrieve annualized revenue, EPS, free cash flow, per-share book value, share-count, and dividend growth for a symbol.
Use this endpoint when you want growth metrics that are already normalized for research, screening, or AI-agent comparisons.
Endpoint
GET /stocks/{symbol}/growth
Test request
/stocks/AAPL/growth
Send a request to view the response.
Authentication
Required.
Authorization: Bearer <your_api_key>
Path Parameters
symbol: ticker or symbol to resolve
What The Endpoint Is Good For
Use growth when you need to:
- compare topline and EPS compounding across stocks
- inspect free-cash-flow and per-share growth without rebuilding annual history
- check whether buybacks are actually shrinking share count
- feed AI-agent prompts with ready-to-use compounding fields
Response
Returns:
metadatagrowth
metadata includes:
symbolas_of_dateperiod_typecurrencycalculation_version
growth includes:
revenue_growth_1yrevenue_cagr_3yrevenue_cagr_5yeps_growth_1yeps_cagr_3yeps_cagr_5yfcf_growth_1yfcf_cagr_3yfcf_cagr_5ybook_value_per_share_growth_1ybook_value_per_share_cagr_3ybook_value_per_share_cagr_5yshare_count_growth_1yshare_count_growth_3yshare_count_growth_5ydividend_growth_3ydividend_growth_5y
Response Notes
- V1 is annual-based and uses the latest imported annual financial history for compounding fields.
- Dividend growth is currently sourced from imported profile growth data.
- Some CAGR fields may be unavailable when the required start point is missing or non-positive.
share_count_growth_*helps distinguish operational growth from dilution or buybacks.
Common Workflow
- Resolve the symbol with Search if needed.
- Call
growthfor annual compounding fields. - Call Fundamental Metrics for quality and leverage ratios.
- Use statement endpoints if you need to audit the raw annual periods behind the growth figures.
Example Request
curl -H "Authorization: Bearer $your_api_key" \
"https://api.apifinance.ai/stocks/AAPL/growth"
Related Endpoints
Next step
Run this endpoint with your own API key
Use the playground to inspect the response first, then create a key and move into implementation once the payload fits your product.