TDAmeritrade | TD Ameritrade Client Library for .NET | Business library

For reasons unknown... changing the --header switch / flag to -H solved the problem. As shown in the following. Spoke with a friend and apparently the shortened form may take different parameters.

You can use the Reverse() method of the JArray class. Just cast your history["candles"] JTokeninto a JArray, and call reverse.

The problem is your data is not in record_path="symbol", it's nested inside callExpDateMap

You have to create a new array and iterate through callExpDateMap and its child json to get the array

The access_type: offline parameter is not a standard in OAuth, but it's used e.g. by Google in their token endpoint request - you must pass it to get a refresh token.

On the other refreshing refresh tokens is part of the OAuth standard. The RFC 6749 states that in a response to the token endpoint:

The authorization server MAY issue a new refresh token, in which case the client MUST discard the old refresh token and replace it with the new refresh token. The authorization server MAY revoke the old refresh token after issuing a new refresh token to the client. If a new refresh token is issued, the refresh token scope MUST be identical to that of the refresh token included by the client in the request.

So it is part of the standard to refresh refresh tokens, but it should be done differently than in their API.

This is official documentation of Newtonsoft method you are trying to use.

https://www.newtonsoft.com/json/help/html/Overload_Newtonsoft_Json_JsonConvert_DeserializeObject.htm

If an API's method returns different json propeties and you cannot trust it's property names all the times, then you can try using a deserialize method that returns .Net object, for example: JsonConvert.DeserializeObject Method (String) https://www.newtonsoft.com/json/help/html/M_Newtonsoft_Json_JsonConvert_DeserializeObject.htm

That method's signature is this: public static Object DeserializeObject(string value)

Parameter is: value of type json string.

Return Value is: Object of type object.

If you do not want an Object, then you can of course use a .Net type you have. Such as this method: JsonConvert.DeserializeObject Method (String)

Any property that you have in both (the .net type and json object) will get populated. If .net type has properties that do not exist in json object, then those will be ignored. If json object has properties that do not exist in.net, then those will be ignored too.

Here's an example of a .Net type

You can deserialize to JObject which has indexer to perform such dynamic querying:

This is probably one of the few times when getting an error message like you did is actually part of the process to authenticate your account. At the very bottom of the PyPi page for that library he explains that you're supposed to copy and paste the resulting url of the error page you're currently on into your terminal. It was confusing for me aswell and it took me awhile to really understand what's going on so I will explain it as best as I can.

Alex Reed is the guy who made the library TD Ameritrade API and he has an awesome YouTube channel called Sigma Coding. One of his video series guides you through the whole process of directly connecting to the TD Ameritrade API without the use of his API library, and another series about building the library itself.

In this video How to Use the TD Ameritrade API | Part 2 he is demonstrating how to access the API. The link should have a time stamp of 16:36 if not skip ahead to that section and you will see a similar error to what you are experiencing except he is using Chrome, not Firefox so the error is the same but worded differently.

Here's a picture to better explain the rest:

What he does next is copy and paste the current url of the page with the error, which contains the code needed for the next step. The url in the picture starts with https://localhost/test?code=siVrfqPLdQ... and you can see that the url has code= following a very long access code that TD Ameritrade needs to generate your access token.

Your url should have a similar structure, don't worry if it doesn't have /test after localhost, he made a specific folder for the video series. Just copy and paste the whole thing in your terminal where you should have a line that says:

Paste the full redirect url here:

TD Ameritrade's API provides an endpoint for market hours however you can't specify which exchange to check, only which market (BOND, EQUITY, ETF etc..).

For some reason, it allows you to specify which date but it only accepts the current date. Providing an access token doesn't do anything so I won't be including a header with the token in my example.

A bit of more details about your usecase would have helped us to analyze the reason behind the program executing too slow. Here are a few considerations:

• A common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux. While it is possible to work around this issue by passing --no-sandbox flag when creating your WebDriver session, such a configuration is unsupported and highly discouraged. You need to configure your environment to run Chrome as a regular user instead. So you may need to drop the --no-sandbox option.

Here is the link to the Sandbox story.

• While using --headless option you won't be able to use --window-size=1280x1696 due to certain constraints.

You can find a couple of relevant detailed discussion in:

• Fullscreen in Headless Chrome using Selenium
• Not able to maximize Chrome Window in headless mode

• The argument --disable-gpu was to enable google-chrome-headless on windows platform. It was needed as SwiftShader fails an assert on Windows in headless mode earlier. This issue was resolved through Headless: make --disable-gpu flag unnecessary

You can find a relevant detailed discussion in ERROR:gpu_process_transport_factory.cc(1007)-Lost UI shared context : while initializing Chrome browser through ChromeDriver in Headless mode

• Further you haven't mentioned any specific requirement of using --hide-scrollbars, --enable-logging, --log-level=0, --v=99, --single-process, --data-path=tmp/data-path, --homedir=tmp, --disk-cache-dir=tmp/cache-dir, --no-proxy-server, --proxy-server='direct://' and --proxy-bypass-list=* arguments which you opt to drop for the time being and add them back as per your Test Specification.

You can find a couple of relevant detailed discussions in:

• Selenium works on AWS EC2 but not on AWS Lambda