Jump to content
  • 0

"Soft 404" error placing orders starting a few months ago


GCone

Question

David Gibbs, who used to be a senior software engineer at IG, wrote some code, based on the original femtotrader code, to allow me to place DMA Equity orders. That was back in 2018. There have been no problems with it until recently.

Below, I have shown the output of two logfiles. The first one is when the DMA order placing software worked (as it did from 2018 until some point in 2023). It failed on the first try, but succeeded on the second. 

The second file shows that I now receive a 404 error trying to place an order.  (The GET function works properly as I am able to retrieve positions). . 

I would like to know whether the URL has changed for the POST function. Thank you.

Here is the successful order placing:

DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.ig.com:443
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/session HTTP/1.1" 200 337
INFO:place_order_PY:Authenticated to IG session for EC.D.ATOFP.CASH.IP order
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/workingorders/dma/equity HTTP/1.1" 200 53
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "GET /gateway/deal/confirms/GG7UZEN2HZ3AX HTTP/1.1" 404 60
INFO:trading_ig.rest:Deal reference GG7UZEN2HZ3AX not found, retrying.
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "GET /gateway/deal/confirms/GG7UZEN2HZ3AX HTTP/1.1" 200 266
INFO:place_order_PY:EC.D.ATOFP.CASH.IP Deal ID Create: DIAAAAKHA5NREBA

Here is the unsuccessful order placing (showing, however, that I am able to retrieve positions):

DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/session HTTP/1.1" 200 337
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "GET /gateway/deal/positions HTTP/1.1" 200 880
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.ig.com:443
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/session HTTP/1.1" 200 337
INFO:__main__:Authenticated to IG session for EC.D.ATOFP.CASH.IP order
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/workingorders/dma/equity HTTP/1.1" 404 123


Output from Python console:

IGException: <html><head><title>Page Not Found</title><h3>Error 404</h3><h3>Sorry, 
the requested page is not available.</h3></body></html>

Thank you for your help.

Kevin Brau

 

 

 

 

Link to comment

4 answers to this question

Recommended Posts

  • 0

As you said, the official REST API  only support OTC orders, not DMA orders.  I cannot trade with OTC orders because I trade small cap equities, which can have enormous spreads.

Furthermore, as I pointed out, /workingorders/dma/equity was an endpoint that used to work from 2018 until around 2023, without any problem. Here is an example of it working:
INFO:place_order_PY:Authenticated to IG session for EC.D.ATOFP.CASH.IP order
DEBUG:urllib3.connectionpool:https://api.ig.com:443 "POST /gateway/deal/workingorders/dma/equity HTTP/1.1" 200 53. (Notice the 200, not 404 code.)  I was also able to delete a working/dma/equity via the deal ID, and update it. 

If I place a DMA equity order via L2, then deal ID is created, which shows that at least DMA equity orders have not been eliminated.  I have read about similar situations where are URL for endpoints is not recognized and no explanation is given. You will never find a reference in the REST API for DMA equity orders enpoints because it is bespoke code, and because there is little demand for it, For me, it's probably a deal breaker. 

Anyway, thanks for your response.  I believe I have to go back to the REST API team, who have already said "this is not our responsibility". It is possible that a decision was taken to remove the workingordres/dma/equity endpoint. I rule nothing out. 

 

 

 

 

 


 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • image.png

  • Posts

    • Anybody following Oil Price?
    • Over the last couple of days, the centre of discussion in the crypto sphere has been about the launching of EIGEN the native token of EIGENLayer. Positioned as one of the biggest project in 2024 with nearly $16B TVL. EIGENLayer is just hovering behind Lido and Aave making it the third- largest protocol on Defi.   With over $64.5M already raised from top prominent heavyweights including Coinbase ventures, Polychain capital and others, the recent partnership with leading tech companies like Near foundation, Polyhedra Network and CELO foundation further cement the high expectation ahead of the launch slated for May 10.   According to information from EIGEN foundation, 15% of the initial 1.67 billion EIGEN token will be airdroped to the community over multiple seasons with 5% set to be distributed on May 10 with one point equating to one token potentially leading to hefty rewards for users. However, several complains has emerged as the token will be initially non-transferable essentially making the cash reward worthless   With lots of tier 1 CEX anticipating the launching of the project, Bitget has launched a pre-market trading for the token for investors to get the token at the best prices pending the official listing. This Ethereum based liquid staking protocol is gearing up massively even though there might be some little hiccups but with the success already recorded so far, I have a feeling this might be the biggest project of 2024. What is your thought on this project?
    • The event is profitable both during market downturn and surge. I feel it's just a way to give back to the community because their is nothing special for the traders to do. They trade, make profits and also get paid decent BGB. Even if they lose while trading, the compensation from the event is reasonable to offset the loss to a reasonable degree.
×
×
  • Create New...
us