‹ EODHD: The Product Lesson 11 of 17
Contents Lesson 11 of 17

5 min read · foundations

Reaching the data without writing code

Why this matters. A large share of the people who need our data cannot call an API and never will. If the only route you can describe involves a package manager, you lost them in the first sentence.

Start with the spreadsheet

The Excel add-in is the answer for the analyst who lives in a spreadsheet, and that is most of the people asking. Historical prices, end of day, intraday and fundamentals arrive as cells in a sheet they already know how to use. If you remember one route from this lesson, it is this one.

The Google Sheets add-on does the same job for the same person on the other platform. Ask which they work in rather than guessing; the answer decides the link.

Alongside both sit ready-made spreadsheets for stocks, ETFs and forex — workbooks with the calls already wired, for someone who wants the data now and the mechanics never.

When the file matters more than the sheet

The downloaders pull end-of-day data as files, for Windows and for Linux. This is the route for the person who wants a folder of CSVs on a schedule rather than a live formula, and it is the standing answer when someone asks for FTP.

The rest of the shelf, and who each is for

Route The person it is for
Power BI connector An analyst building dashboards for other people to read
WordPress plugin Somebody publishing quotes on a site they already run
Chrome extension A person who wants a price bar and a converter while they browse
XLQ2 integration An existing XLQ2 user, who will name it themselves
NinjaTrader adapter A trader who wants our EOD, intraday and fundamentals inside their platform
Telegram bot Someone who wants signals pushed to them and nothing else

Read that table as a matching exercise rather than a list to recite. The question that picks the row is never "which tool is best" — it is where does this person already work? Answer that and the route is decided, usually in one sentence.

What none of them do

Every route here is read-only, and every one is bounded by the plan behind the key. A no-code tool does not widen entitlement: if the account does not carry fundamentals, the add-in will not conjure them. When somebody reports that a tool "is missing data", the plan is the first thing to check and the tool is usually the last.

Try it now

Take the last three people who asked you for data and place each on the table above — including the one you sent to the API. For any you cannot place, write the question you would have needed to ask them. That question is the one worth asking first next time.