-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for Tiingo financial statements API #301
Comments
Thanks for suggesting this! I 100% agree with adding it. My only recommendation is that we wait until it's out of beta before including it in a quantmod release. Feel free to start coding and testing though! |
Apologies to all. I have not had a chance to work on this and it just keeps getting bumped down in priority for me. I do hope to get to it at some point, but probably will not be for a good while longer |
No need to apologize! I mentioned this in 327 because it's an example of what needs to be done for |
primitive baseline initial functionality. still very much a WIP. feedback welcome: |
Hi @tiingo, we have a working version of this. is this financial statement API still considered to be beta? |
Thanks for the report Ethan! @tiingo, is this expected behavior? Would it be possible to make the JSON always have the same fields, even if they're empty/null? |
This comment has been minimized.
This comment has been minimized.
Response from tiingo: needed changes have been pushed: |
@tiingo is working on a financial statement API: https://api.tiingo.com/documentation/fundamentals
I think we should support this through the
getFinancials
function (which currently has no live implementations)I'll get started on a PR, unless there are any objections
The text was updated successfully, but these errors were encountered: