-
Notifications
You must be signed in to change notification settings - Fork 47
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
Non 200 response #9
Comments
It's exactly the same issue I opened 10 hours before you... |
I'm looking at this right now... |
I think your problem is the '@AMER.OAUTHAP' at the end of your client_id. Do NOT include that part. I only am using the client ID with is 32 alphanumeric digits (uppercase) long. Take out the @AMER.OAUTHAP and see if it works. |
I tried that already, same error message. |
This worked for me. It's a Junit test, but you can just run a main method instead using
|
That worked for me. Can you try an easier test and just do something like:
It's possible you don't have the access to price history calls depending on your account level at TDA. |
I created a fresh new repo in my IDE and did a git clone instead of just downloading the source and required libraries via pom.xml. Then I built a jar for the entire project and added that to the classpath of my project. Did the trick. Thanks for the code! |
Hi there,
I got the response through https://api.tdameritrade.com/v1/oauth2/token successfully. I then copied the refresh token and client id (from app I created) into the properties as follows:
I keep getting this error for all API calls:
Exception in thread "main" java.lang.RuntimeException: Non 200 response: [404 - /v1/marketdata/FB/pricehistory] - https://apis.tdameritrade.com/v1/marketdata/FB/pricehistory
at com.studerw.tda.client.HttpTdaClient.checkResponse(HttpTdaClient.java:622)
at com.studerw.tda.client.HttpTdaClient.priceHistory(HttpTdaClient.java:165)
at com.tdameritrade.PlayGround.play1(PlayGround.java:54)
at com.tdameritrade.PlayGround.main(PlayGround.java:22)
Any ideas?
Thanks.
The text was updated successfully, but these errors were encountered: