Finnhub API

Name: Finnhub API
Brand: Finnhub API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey108 EndpointsREST

For Agents

Query real-time stock quotes, company fundamentals, news, earnings, crypto and forex data, and economic indicators across global markets. Includes an AI Copilot endpoint for natural-language financial questions.

Install Jentic One Beta

Connect the Finnhub API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Finnhub API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Finnhub API.

Pull real-time stock quotes, candles, and tick data for global equities across 60+ exchanges

Retrieve company fundamentals including financials-as-reported, peers, ownership, and ESG scores

Fetch earnings calendars, IPO calendars, and economic event calendars with consensus estimates

GET STARTED

Start building with Finnhub API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Finnhub API, keeping it validated and agent-ready. Finnhub is a real-time financial data API providing institutional-grade market data, fundamentals, alternative data, and news for global stocks, forex, crypto, bonds, ETFs, and economic indicators. Coverage spans 60+ exchanges with company financials, earnings calendars, insider transactions, analyst estimates, sentiment scores, and an AI Copilot endpoint for natural-language financial queries. The 108 endpoints make it suitable for trading research, portfolio analytics, and agent-driven market intelligence pipelines.

Use Cases

Patterns agents use Finnhub API for, with concrete tasks.

★ Real-Time Trading Research

Power systematic and discretionary trading workflows with real-time quotes, candles, and order book data for stocks, ETFs, forex, and crypto. Finnhub serves institutional-grade tick data through endpoints like /quote, /stock/candle, and /forex/candle, enabling backtests and live signal generation against 60+ exchanges. Integration takes a few hours with the apiKey query parameter.

Fetch the last 30 days of daily candles for AAPL, NVDA, and MSFT from /stock/candle and compute the 20-day rolling correlation matrix

Earnings and Calendar Tracking

Build earnings dashboards and event-driven trading alerts using the /calendar/earnings, /calendar/ipo, and /calendar/economic endpoints. Each calendar entry includes consensus estimates, prior values, and surprise calculations, so agents can flag earnings beats and macro releases without scraping investor relations pages. Setup takes under an hour.

Pull the next 7 days of earnings releases from /calendar/earnings filtered to S&P 500 tickers and post a summary to Slack

Alternative Data and Sentiment

Enrich research notes with insider transactions, lobbying spend, senate trading disclosures, social sentiment, and news sentiment scores. Finnhub aggregates these alternative signals into per-ticker endpoints like /stock/insider-transactions and /news-sentiment, which agents can poll alongside price data to detect divergences. A typical sentiment integration is live the same day.

Compare /stock/insider-transactions for TSLA over the last 90 days against /news-sentiment scores and flag weeks where insider sales coincided with negative sentiment

AI Agent Market Intelligence

Use Finnhub through Jentic so agents answer multi-step market questions without juggling endpoints. The /ai-chat Copilot accepts natural-language queries, while structured endpoints back deeper analysis. Jentic exposes both as discoverable tools so an agent can answer 'What is the consensus EPS for AAPL Q4?' or 'Pull NVDA insider sales' through the same search-load-execute flow. Get started with Jentic One, the self-hosted execution layer

Through Jentic, search 'get stock fundamentals', load the /stock/metric schema, and execute a call for ticker AAPL with metric=all

Key Endpoints

108 endpoints — jentic publishes the only available openapi specification for finnhub api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/quote

Real-time quote for a symbol

GET

/stock/candle

OHLCV candle data for stocks

GET

/calendar/earnings

Upcoming earnings with consensus estimates

GET

/calendar/ipo

Upcoming IPO calendar

GET

/company-news

News articles for a company

GET

/crypto/candle

OHLCV candles for crypto pairs

POST

/ai-chat

AI Copilot natural-language financial queries

GET

/quote

Real-time quote for a symbol

GET

/stock/candle

OHLCV candle data for stocks

GET

/calendar/earnings

Upcoming earnings with consensus estimates

GET

/calendar/ipo

Upcoming IPO calendar

GET

/company-news

News articles for a company

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Finnhub token is stored once, encrypted, by your own Jentic One instance and injected as the token parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a stock quote' or 'pull the earnings calendar', and Jentic returns the matching Finnhub operation with its input schema so the agent calls the right one of 108 endpoints without browsing the reference docs.

Time to first call

FAQs

Specific to using Finnhub API through Jentic.

Why is there no official OpenAPI spec for Finnhub API?

Finnhub does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Finnhub API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Finnhub API use?

Finnhub uses an API key passed as the `token` query parameter on every request. Through Jentic, the key is held in the encrypted vault and injected at execution time so it never enters the agent context.

Can I get real-time quotes with the Finnhub API?

Yes. The /quote endpoint returns current price, daily high/low, previous close, and timestamp for any supported symbol. Free-tier delays apply for some exchanges; premium tiers stream real-time US equities.

What are the rate limits for the Finnhub API?

The free tier allows 60 API calls per minute. Premium tiers raise this substantially and unlock real-time and intraday endpoints. Rate-limit headers are returned on every response so agents can back off automatically.

How do I pull earnings data through Jentic?

Search Jentic for 'get earnings calendar', load the /calendar/earnings schema, then execute with a `from` and `to` date range. Jentic returns the structured response your agent can act on without any HTTP plumbing.

Does Finnhub cover crypto and forex?

Yes. The /crypto/candle, /crypto/symbol, and /forex/candle endpoints provide OHLCV data across multiple exchanges and currency pairs, suitable for cross-asset agent strategies.

Can I limit what my agent is allowed to do with the Finnhub API?

Yes. Because you run Jentic One yourself, you decide which of the Finnhub API's 108 operations your agent may call, so you can allow just the ones it needs, such as /quote lookups, the /calendar/earnings feed, and /company-news, and leave everything else out of the allowed set. Since Finnhub passes its target as query parameters rather than as an owned URL path resource, this operation-level allowlist is how you keep the agent scoped to the data it should touch. Your own rules also govern the stored token, so the agent only reaches Finnhub through the calls you have permitted.