Close Position Using rest API

[Guest oliver3146]

Hi all,

I'm currently using IG rest API top open and positions. I don't have any issue opening a position but when I try to close it I get below error message:

"errorCode": "validation.mutual-exclusive-value.request"

I also get this error when using API companion:

Deal Id: DIAAAADQNQBZCAH

Epic: IX.D.SPTRD.IFE.IP

Expiry: -

Direction:  SELL (because my position is BUY)

Deal Size: 1

Closing order Level: 

Order Type:  MARKET

Time In Force: 

Quote ID: 

 (DELETE /positions/otc)

 

After I press GO I get error: "errorCode": "validation.mutual-exclusive-value.request" the same I get using python API.

Could you please help ? What am I doing wrong?

 

Thanks in advance

[JulianG]

I think you need to leave the Epic blank. There reference page says:

[Constraint: Set only one of {dealId,epic}]

See https://labs.ig.com/rest-trading-api-reference/service-detail?id=542

Also, I'm not sure about the SELL. I've a feeling that I have had to use the same direction as my original trade, but I couldn't be 100% sure. It's worth checking.

Julian

[MossOnTheTree]

If anyone is still having this problem, the answer is to use the POST method on your httpClient obj (whatever you're using) and set a header value. ("_method": "DELETE")

It needs to be POST because you're adding a request body, which isn't supposed to work with the DELETE verb.

So a request will look like this:

Method: POST

POST body:
{
    "dealId": "<deal id>",
    "direction": "SELL",
    "size": "1",
    "orderType": "MARKET",
}
All the rest could be null

Headers:
X-IG-API-KEY: <your api key>
X-SECURITY-TOKEN: <your token from logging in>
CST: <your cst token from logging in>
Content-Type: application/json
Version: 1
_method: DELETE

Hope this helps

[ships1980]

On 05/05/2020 at 19:14, Guest oliver3146 said:

Hi all,

I'm currently using IG rest API top open and positions. I don't have any issue opening a position but when I try to close it I get below error message:

"errorCode": "validation.mutual-exclusive-value.request"

I also get this error when using API companion:

Deal Id: DIAAAADQNQBZCAH

Epic: IX.D.SPTRD.IFE.IP

Expiry: -

Direction:  SELL (because my position is BUY)

Deal Size: 1

Closing order Level: 

Order Type:  MARKET

Time In Force: 

Quote ID: 

 (DELETE /positions/otc)

 

After I press GO I get error: "errorCode": "validation.mutual-exclusive-value.request" the same I get using python API.

Could you please help ? What am I doing wrong?

 

Thanks in advance

 

[ships1980]

I am also getting the same error.  Can someone help me.

 

[ArvinIG]

15 minutes ago, ships1980 said:

I am also getting the same error.  Can someone help me.

 

Hi @ships1980,

You can try to reach out to webapisupport@ig.com , the API support might be able to help you.

All the best - Arvin 

[ships1980]

@ArvinIG Thank you. Solved the issue.

[Guest Simon]

Deal Id: DIAAAADQNQBZCAH
Epic:
Expiry:
Direction:  SELL (because my position is BUY)
Deal Size: 1
Closing order Level:
Order Type:  MARKET
Time In Force:
Quote ID:

 (DELETE /positions/otc)

When i send this request via command: "Call oXMLHTTP.SEND(requestBodyString)"

i get this error: "errorCode": "validation.null-not-allowed.request"

if i copy request text to API companion . It runs perfectly

Any body got a solution to this?

[Guest simon]

request body string :{"dealId":"DIAAAAGVJZBK3AZ","direction":"SELL","size":"1","orderType":"MARKET","timeInForce":"EXECUTE_AND_ELIMINATE"}
Method : (DELETE /positions/otc)
When i send this request via command: "Call oXMLHTTP.SEND(requestBodyString)"
i get this error: "errorCode": "validation.null-not-allowed.request"
if i copy request text to API companion . It runs perfectly

Any body got a solution to this?

[Sjg1234]

request body string :{"dealId":"DIAAAAGVJZBK3AZ","direction":"SELL","size":"1","orderType":"MARKET","timeInForce":"EXECUTE_AND_ELIMINATE"}
Method : (DELETE /positions/otc)
position : "BUY"
When i send this request via command: "Call oXMLHTTP.SEND(requestBodyString)"
i get this error: "errorCode": "validation.null-not-allowed.request"
if i copy request text to API companion . It runs perfectly

Any body got a solution to this?

[JulianG]

Are you definitely sending a DELETE and not a GET or a PUT?

[Sjg1234]

yes its definitely a DELETE

Call oXMLHTTP.Open("DELETE", IG_API_HOST + "/positions/otc", False)

 

 

Edited October 28, 2021 by Sjg1234

[JulianG]

Try this https://labs.ig.com/node/570

[Sjg1234]

thanks @JulianG we got it working,
 

Really appreicate that 😀

[ships1980]

On 28/10/2021 at 18:14, Guest Simon said:

Deal Id: DIAAAADQNQBZCAH
Epic:
Expiry:
Direction:  SELL (because my position is BUY)
Deal Size: 1
Closing order Level:
Order Type:  MARKET
Time In Force:
Quote ID:

 (DELETE /positions/otc)

When i send this request via command: "Call oXMLHTTP.SEND(requestBodyString)"

i get this error: "errorCode": "validation.null-not-allowed.request"

if i copy request text to API companion . It runs perfectly

Any body got a solution to this?

I think so expiry needs a '-' as value.

 

[jlz]

Can you post the request headers? 

This error is related to a wrong header value. 

If you can't make the DELETE method to work use the POST method and set the _method header to DELETE.

https://labs.ig.com/node/570

[Hristo_K]

@Sjg1234 Hi, I am having exactly the same issue. where the API companion works, but exactly the same request gives error in node.js. Would you please share how did you manage to make it work?

The shared links above no longer work.

Many thanks,

Hristo

[Alpha007]

I am also running into issue when trying to delete a position when following payload 

{
   "dealId": "DIAAAAJBD8TYKAT",
   "direction": "SELL",
   "orderType": "MARKET",
   "timeInForce": "FILL_OR_KILL",
   "size": 1.16,
   "expiry": "DFB"
}

 

endpoint https://demo-api.ig.com/gateway/deal/positions/otc

when I use POST method with _method header as DELETE, it returns 

{

"errorCode": "error.service.marketdata.position.notional.details.null.error"

}

 

when I use DELETE method 

validation.null-not-allowed.request

 

Will appreciate any help in this regard. 

[JulianG]

Looking at the API documentation, I would leave expiry and timeInForce blank. The direction should be the opposite of the direction when the position was opened. And I use POST with _method DELETE, as you are.

Julian

[SUPAD]

Thanks @MossOnTheTree, this helped me a lot !

 

[KML]

Where you able to get this to work? When I add the _method = DELETE header, I get a 404 file not found, but I've checked the URI about 718 times. I'm able to create new positions, and also to delete using the API companion.

The following is a printout from my post() method when creating a position:

IgAPI.post: URI: https://demo-api.ig.com/gateway/deal/positions/otc
IgAPI.post: Headers: java.net.http.HttpHeaders@2c272c73 { {Accept=[application/json; charset=UTF-8], Content-Type=[application/json; charset=UTF-8], CST=[removed], IG-ACCOUNT-ID=[removed], Version=[2], X-IG-API-KEY=[removed]} }
IgAPI.post: Body: {"currencyCode":"USD","direction":"BUY","epic":"IX.D.SPTRD.IFM.IP","expiry":"-","forceOpen":"true","guaranteedStop":"false","orderType":"MARKET","size":"0.04","stopDistance":"2","trailingStop":"true","trailingStopIncrement":"1"}

which works.

And the following is the same printout when trying to delete a position:

IgAPI.post: URI: https://demo-api.ig.com/gateway/deal/positions/otc
IgAPI.post: Headers: java.net.http.HttpHeaders@42f3e43d { {_method=[DELETE], Accept=[application/json; charset=UTF-8], Content-Type=[application/json; charset=UTF-8], CST=[removed], IG-ACCOUNT-ID=[removed], Version=[2], X-IG-API-KEY=[removed]} }
IgAPI.post: Body: {"dealID":"DIAAAAPN7BCT8AP","direction":"SELL","size":"0.04","orderType":"MARKET"}

which yields a 404 response.

Any help highly appreciated!
 

[JulianG]

The only thing I can see is the version, which should be 1 for DELETE and not 2.

[KML]

Thanks! 🙂 Tested and works with version 1. I sort of remember that I changed to version 2 a few months back, but I don't remember why, and the program still seems to work. (That code is also used during log in and creation of position.)

Not sure why that lead to 404, but now I'm past that hurdle. 

[JulianG]

Looking at the API documentation, it seems that each call has version 1, and maybe other later versions. I assume we ought to use the latest version for a new application, but the older versions remain so things don't break. e.g. You would use version 2 (the latest) to create a position and version 1 (the only one) to close it.

Julian