FinData home · Developers · About · Contact

FinData API developer guide

FinData provides a read-only financial data API for exploring SEC-reported company fundamentals, filing facts and corporate-action facts. Coverage varies by company and filing.

Free self-service access

Free launch access is available without a credit card. Create an account or sign in, then use the self-service token page to obtain a short-lived API token. Paid plans are not active. The production API is read-only and uses live data. Try the free sandbox without an account; it serves fictional data through a limited read-only test API and does not cover authentication or the full API.

Make a request

Send the token as a bearer credential. For example, search for a company:

curl -H "Authorization: Bearer YOUR_TOKEN" "https://api.findata.com/v1/companies?query=apple"

Use GET /v1/metrics to list metric definitions and GET /v1/companies/AAPL/metrics/series?metrics=revenue&frequency=annual for a reported series. Follow returned pagination fields where provided. Values and their limitations should be checked against their source filings.

See the API reference, OpenAPI specification, and MCP documentation. OAuth clients can discover the authorization server via protected resource metadata. Tokens must target https://api.findata.com and should be kept secret.

Command-line client

Download the read-only Node.js CLI (Node.js 20 or later), set FINDATA_TOKEN to your short-lived token, then run node findata-cli.mjs get "/v1/companies?query=apple". The client sends credentials only to api.findata.com and rejects redirects. Keep tokens out of source control and command histories.

Errors, limits and versions

JSON errors include a stable code and a message. A 429 response includes Retry-After in seconds. RateLimit-Policy describes the configured limit and window; remaining requests and reset times are not available. API paths are versioned under /v1/. Breaking changes are intended for a new major version; deprecations will be documented and signalled with Deprecation and Sunset headers where applicable. No retirement date is currently scheduled. Read the API versioning and deprecation policy.