You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
endpoint, when you close a position. The method in this project is IGService.fetch_deal_by_deal_reference(). This is the request you make after opening/updating/closing a position or working order. It responds with the status of your request, and a unique ID for the transaction, if it was successful.
The bug is this: when closing a position, fetch_deal_by_deal_reference() responds with the ID of the opening transaction, not closing. There is a discussion about it on the IG community forum here.
This a real pain. Especially as IG don't even acknowledge that there is anything wrong. It makes it hard to associate opening and closing trades, and therefore get P&L information.
There is a workaround, as outlined in the forum chat. I propose to add built-in support for the workaround in the code. Optional of course.
The same bug exists whether you request the confirms information via the REST or Streaming API
The text was updated successfully, but these errors were encountered:
There is a bug in IG's implementation of their
endpoint, when you close a position. The method in this project is
IGService.fetch_deal_by_deal_reference()
. This is the request you make after opening/updating/closing a position or working order. It responds with the status of your request, and a unique ID for the transaction, if it was successful.The bug is this: when closing a position,
fetch_deal_by_deal_reference()
responds with the ID of the opening transaction, not closing. There is a discussion about it on the IG community forum here.This a real pain. Especially as IG don't even acknowledge that there is anything wrong. It makes it hard to associate opening and closing trades, and therefore get P&L information.
There is a workaround, as outlined in the forum chat. I propose to add built-in support for the workaround in the code. Optional of course.
The same bug exists whether you request the
confirms
information via the REST or Streaming APIThe text was updated successfully, but these errors were encountered: