Why does the API return a 404 for my ticker?
What entity_not_found, no_coverage, ticker_is_etf and ticker_is_index mean, and what to do for each.
A 404 on a per-ticker endpoint means there is nothing to return, and the error code in the response says why. Each code has a different next step.
error |
What it means | What to do |
|---|---|---|
entity_not_found |
We track no stock by that symbol | Check the suggestions in the response, or search the company name, then retry with the real symbol |
no_coverage |
We track the symbol but have no data of that kind for it | Stop retrying this symbol on this endpoint. A different spelling will not help |
ticker_is_etf |
The symbol is a fund, so the question does not apply | Call one of the fund endpoints listed in seeInstead |
ticker_is_index |
The symbol is a market index | Call one of the fund endpoints listed in seeInstead |
Common causes
- The symbol is from a non-US exchange. Every ticker endpoint works on US-listed securities. For a foreign company, use its US-listed symbol, the ADR, not a home-market symbol such as
SAP.DE. - The path is in the wrong order. Check the endpoint against the API reference. A path with the ticker in the wrong place also returns a 404.
- It is a fund on a stock endpoint. Funds have their own endpoints.
An empty result is different from a 404. A known company with no readings in the requested window returns an empty 200 on the metrics endpoint.
More in API and MCP
Plans and billing: see the FAQ. Still stuck? Contact us.