Finnhub API: Quota Units, Coverage & Use Checklist
Inspect Finnhub documented data scope, access boundaries and a concrete integration-verification task.
Data workflow
Stock, forex, crypto and financial research endpoints are described by the provider; entitlement is endpoint-specific.
Documented quota and access
The general documentation states an additional 30 calls/second ceiling above plan limits. A current numeric free-plan quota is not asserted; verify the actual account entitlement.
Use and display boundaries
Verify the exact account quota, exchange coverage and personal versus business/display permissions before selecting a feed. Unknown limits are not treated as unlimited.
A practical acceptance task
Open the required endpoint documentation under the intended account and record the permitted symbols, response shape, timing and active rate-limit policy. This catalogue did not authenticate an API key.
Keep the request context
Record endpoint/version, instrument identity, data frequency, timezone, history range, adjustment flags and the account entitlement. Retain only the response/provenance that the applicable terms permit. A generic provider comparison cannot replace a named dataset specification.
Test semantics before scale
Use a small authorized example and inspect status, response schema and any error object inside a successful HTTP response. Check pagination and row ordering. The local daily inspector accepts an explicitly mapped single-series CSV; it is not a universal provider JSON adapter or a certification of source accuracy.
Primary evidence
Finnhub API documentation — checked 17 October 2026. Numeric limits are omitted where no current primary-source plan value was verified; omitted does not mean unlimited.
Inspect a daily OHLCV CSV locally · Compare documented API workflows