Skip to content

Quick Start

Make your first API request to retrieve Apple’s balance sheet:

Terminal window
curl https://api.finpoint.dev/api/v1/financial-statements/balance-sheet/AAPL

Authentication

All API requests require an API key. Include it as a Bearer token in the Authorization header:

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" https://api.finpoint.dev/api/v1/financial-statements/balance-sheet/AAPL

Note: Sign up at finpoint.dev to get your free API key.

Base URL

All endpoints are served from:

https://api.finpoint.dev/api/v1

Endpoints Overview

The API exposes four categories of financial data:

CategoryDescription
Financial StatementsIncome statement, balance sheet, and cash flow statement data
Financial RatiosPre-computed financial ratios with A–F letter grades
Company ProfilesTicker metadata, sector, industry, and exchange info
Ticker DirectoryList of all available companies

Making Your First Request

Income Statement

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/financial-statements/income-statement/MSFT"

Balance Sheet

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/financial-statements/balance-sheet/AAPL"

Cash Flow Statement

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/financial-statements/cashflow-statement/AMZN"

Financial Ratios

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/financial-ratios/ratios/NVDA"

TTM Aggregation (Trailing Twelve Months)

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/financial-statements/income-statement/AAPL?period=ttm"

Flow metrics are summed over the last 4 quarters; balance sheet items use the latest value. See the TTM guide for full details.

Company Profile

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/company/NVDA"

Available Tickers

Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.finpoint.dev/api/v1/tickers"

Common Query Parameters

All data endpoints support these optional parameters:

ParameterTypeDefaultDescription
periodstringquarterlyPeriod type filter: annual, quarterly, or ttm
fyintegerFilter by fiscal year (e.g. 2024). Omit for no filter.
fiscal_periodstringExact fiscal period: FY, Q1, Q2, Q3, Q4
limitinteger4Number of most recent periods to return

Note: The old flat paths (/api/v1/income-statement/{ticker}, /api/v1/balance-sheet/{ticker}, /api/v1/cashflow-statement/{ticker}, /api/v1/as-reported/{ticker}, /api/v1/financial-ratios/{ticker}) still work but are deprecated and will be removed in a future release. | format | string | pivoted | Response format: pivoted (grouped by period) or flat (legacy row format) | | as_of | date | — | Point-in-time filter (YYYY-MM-DD). Only data from filings on or before this date. | | cik | string | — | CIK identifier as alternative to ticker (e.g. 0001045810) | | metrics | string | — | Comma-separated list of metric names to filter (e.g. TotalRevenues,GrossProfit) |

Response Format

The default response format is pivoted — periods are grouped, and line items appear as a key-value map within each period:

{
"ticker": "AAPL",
"company_name": "Apple Inc.",
"statement_type": "IncomeStatement",
"periods": [
{
"fiscal_year": 2024,
"fiscal_period": "FY",
"period_end_date": "2024-09-28",
"period_start_date": "2023-09-30",
"filing_date": "2024-10-31",
"form_type": "10-K",
"currency": "USD",
"line_items": {
"TotalRevenues": 383285000000,
"GrossProfit": 139323000000,
"OperatingIncomeLoss": 103568000000,
"NetIncomeLoss": 93736000000
}
}
]
}

Note: The legacy flat row format (one row per metric-period pair) is available by appending ?format=flat.

Next Steps

  • Browse the Endpoint Reference for detailed per-endpoint docs
  • Read the Data Model overview to understand the warehouse schema
  • Learn about TTM — server-side aggregation via ?period=ttm
  • Review XBRL Caveats to understand data quality considerations