EODHD Financial Data API

Name: EODHD Financial Data API
Brand: EODHD Financial Data API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey68 EndpointsREST

For Agents

Pull historical and real-time stock prices, fundamentals, news sentiment, and macro indicators for thousands of tickers across 70+ exchanges. Authenticate with a single api_token query parameter.

Install Jentic One Beta

Connect the EODHD Financial Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EODHD Financial Data 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 EODHD Financial Data API.

Retrieve end-of-day OHLCV history for any ticker on a supported exchange

Fetch company fundamentals including financial statements, ratios, and ESG scores

Pull earnings, IPO, splits, and dividend calendars filtered by date range

GET STARTED

Start building with EODHD Financial Data API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use EODHD Financial Data API for, with concrete tasks.

★ Quantitative Backtesting Data Pipeline

Quant researchers and trading bots need clean historical OHLCV plus corporate actions to backtest strategies. EODHD covers over 70 exchanges with adjusted prices, dividends, and splits in a single normalised API, so an agent can populate a strategy database without per-vendor adapters. Universe sweeps run in minutes once the api_token is loaded.

Fetch 10 years of daily adjusted closes for the S&P 500 constituents via /eod/{ticker} and write the results to a parquet file.

Fundamentals-Based Screening for Investment Research

Analysts running thematic or value screens need to filter the global equity universe by reported fundamentals. The /screener and /fundamentals endpoints let an agent combine valuation ratios, growth metrics, and ESG flags into a single ranked list of tickers, replacing manual exports from terminals.

Call /screener with filters market_cap>1e9, pe<12, dividend_yield>0.03 and return the top 50 results sorted by yield.

News Sentiment Monitoring for a Watchlist

Portfolio managers track headline risk on holdings by aggregating sentiment-scored news. EODHD attaches sentiment polarity and magnitude to each article via /news and /sentiments, so an agent can flag tickers with sharp sentiment shifts and trigger alerts before price moves.

Pull the last 24 hours of news for tickers AAPL, MSFT, GOOG via /news and return any article with sentiment polarity below -0.5.

AI Agent Market Data Tool via Jentic

An AI agent embedded in a finance copilot needs on-demand market data without bespoke client code. Through Jentic the agent searches for the EODHD operation by intent (for example 'get historical stock prices'), loads the schema, and executes the call with a vault-stored api_token. No SDK installation or per-endpoint integration is required.

Use Jentic search('get historical stock prices'), load the matching EODHD operation, and execute it for ticker TSLA.US over the last quarter.

Key Endpoints

68 endpoints — jentic publishes the only available openapi specification for eodhd financial data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/eod/{ticker}

End-of-day historical prices

GET

/fundamentals/{ticker}

Company fundamentals and financial statements

GET

/screener

Run a fundamentals and valuation screener

GET

/news

Financial news with sentiment scores

GET

/calendar/earnings

Upcoming earnings calendar

GET

/technical/{ticker}

Technical indicator series

GET

/macro-indicator/{country}

Macroeconomic indicators by country

GET

/exchange-symbol-list/{exchangeCode}

List symbols traded on an exchange

GET

/eod/{ticker}

End-of-day historical prices

GET

/fundamentals/{ticker}

Company fundamentals and financial statements

GET

/screener

Run a fundamentals and valuation screener

GET

/news

Financial news with sentiment scores

GET

/calendar/earnings

Upcoming earnings calendar

Why Jentic?

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

Credential isolation

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

Intent-based discovery

Agents search Jentic by intent such as 'historical stock prices' or 'company fundamentals', and Jentic returns the matching EODHD operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using EODHD Financial Data API through Jentic.

Why is there no official OpenAPI spec for EODHD Financial Data API?

EODHD does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the EODHD Financial Data 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 EODHD Financial Data API use?

EODHD uses an apiKey scheme passed as the api_token query parameter on every request. Through Jentic the token is stored encrypted in your Jentic One instance, and agents receive a scoped reference rather than the raw token in their context.

Can I pull historical end-of-day prices with the EODHD Financial Data API?

Yes. The GET /eod/{ticker} endpoint returns daily OHLCV history for a ticker on any of the 70+ supported exchanges, with adjustments for splits and dividends available via query parameters.

What are the rate limits for the EODHD Financial Data API?

EODHD enforces per-plan request limits (commonly 1,000 to 100,000 calls per day depending on subscription) and a per-second cap. The OpenAPI spec does not encode these; check your plan dashboard at eodhd.com for the current numbers.

How do I screen stocks by fundamentals through Jentic?

Search for the operation with query 'screen stocks by fundamentals'. Jentic returns the GET /screener operation, you load its schema, and execute with filter expressions on market_cap, pe, dividend_yield, and other fields. The scoped api_token is injected automatically.

Can I get news sentiment for a specific ticker?

Yes. GET /news accepts a ticker filter and returns articles with sentiment polarity and magnitude attached. For aggregate sentiment series use GET /sentiments with the same ticker filter.

Is the EODHD Financial Data API free?

EODHD offers a limited free tier for evaluation and paid subscriptions starting around USD 19.99/month for the All-In-One plan, with higher tiers unlocking fundamentals, intraday, and bulk endpoints. See eodhd.com/pricing for current rates.

Can I limit what my agent is allowed to do with the EODHD Financial Data API?

Yes. Because you run Jentic One yourself, your own rules decide which EODHD operations and credentials the agent may use, and you grant only the ones it needs. Since EODHD is read-only reference data, you can allow just GET /eod/{ticker} for historical prices or GET /fundamentals/{ticker} for company financials while leaving everything else out of reach. The screener at GET /screener or the news feed at GET /news is callable only if you add it to that allowed set. Your api_token is stored encrypted by your own instance and injected at execution time, so the agent never sees the raw key.