Skip to content

Conversation

@JNewman-cell
Copy link

@JNewman-cell JNewman-cell commented Oct 24, 2025

Summary

When calling any quoteSummary-based property (such as asset_profile, earnings, financial_data, key_stats, etc.) via the yahooquery package, the returned values exhibit inconsistent response structures depending on the ticker and asset type:

For many well-known tickers (e.g. AAPL) these properties return a dictionary mapping a normalized ticker key to a nested dict with structured data (expected structure).
For many other tickers (e.g. EAI) the same properties return a dict mapping the ticker to a plain string error message, e.g. {'EAI': 'No fundamentals data found for symbol: EAI'} (unexpected structure).

This systematic inconsistency affects 15 out of 17 quoteSummary properties and causes downstream code that expects consistent dict-of-dicts structures to fail or misinterpret responses across different asset classes.
Real-world Impact

This GitHub Actions run is a real-world example of someone expecting a parsable JSON response yet receiving an unexpected response from the API.

https://github.com/JNewman-cell/StockInformationWebsiteGithubActions/actions/runs/18789336097/job/53615494426
Behavior
Old Response: {'EAI': 'No fundamentals data found for symbol: EAI'}
New Response: { "error": { "code": 404, "type": "NotFoundError", "message": "No fundamentals data found for symbol: EAI", "symbol": "EAI" } }

@JNewman-cell
Copy link
Author

@dpguthrie @maread99 I fixed this issue I was running into personally, there is more documentation here if you need to read through it
https://github.com/JNewman-cell/YahooQueryBugFix

JNewman-cell added a commit to JNewman-cell/StockInformationWebsiteGithubActions that referenced this pull request Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant