Order only succeeds when logged in once via browser

I do have some strange errors when ordering:

2022-03-09 18:37:57,586 CRITICAL MainThread      400
2022-03-09 18:37:57,586 CRITICAL MainThread      {"errors":[{"text":"order.error.128"}]}

2022-03-14 11:42:02,077 CRITICAL MainThread      500
2022-03-14 11:42:02,077 CRITICAL MainThread      {"errors":[{"text":"Internal server error"}]}

Unfortunately there is no more debug output despite I set

level=logging.DEBUG

I just found out that at least the

{"errors":[{"text":"Internal server error"}]}

error is gone, when I login to degiro once via browser. I guess this is a bug. The session is created correctly:

2022-03-14 12:08:17,645 INFO MainThread get_session_id:response_dict: {'isPassCodeEnabled': True, 'locale': 'de_DE', 'redirectUrl': 'https://trader.degiro.nl/trader/', 'sessionId': 'xxxxxxxxx.prod_a_116_4', 'status': 0, 'statusText': 'success'}

Might always happen after a weekend, when I did not login for a long time, but not sure. No, happened this morning again. Always have to login first, until buy order is executed.

[TommasoBendinelli]

I agree that the login process for the web portal is different from DeGiro’s API connect() method. I have noticed that if you log in via the browser or your phone, no errors pop up until midnight of the next day . So right now I am logging in into Degiro every morning as workaround, so that I am sure my daily orders will go through. But it isn’t very pleasant experience, and goes against principle of having automated API where everything supposed to be automated without user intervention.

[funnel20]

@coveritytest I’m glad you brought this up, since I have the same experience. It’s certainly not related to a timeout issue between consecutive API calls, see my remark in this post.

Work-around

1. Our script with the DeGiro Connector (API) runs dedicated on laptop 1.
2. We start it 1.5 hours before New York Market opening and let it run for 9 hours in total
3. Together with the start of the script, we login to DeGiro web portal on laptop 2.
4. After a random amount of time, the web portal on laptop 2 is logged out automatically.
5. Orders created with the API on laptop 1 will be executed without issues.

When we omit step 3, step 5 will fail with errors.

Observations

• Since we use 2 different laptops, nothing can be set on the local machine. So DeGiro must link something to the account.
• Since the API error is introduced after time (i.e. when not logged in to the web portal for 1 day) it seems to relate to something as an OAuth expiration.
• Apparently the login to the web portal does something else to the DeGiro account server, than the API connect() method. @Chavithra Do you have any idea what this difference might be?