error.service.marketdata.position.details.null.error

7 posts / 0 new
Last post
RUSSEPAT
error.service.marketdata.position.details.null.error

When updating a position's stop level, I receive this error intermittently and the update fails.

I can produced the error using EUR/USD DFB on the demo environment. It can be replicated using the API companion.

What does this error mean and why does it occur?

RUSSEPAT
error.service.marketdata

error.service.marketdata.position.details.null.error

RUSSEPAT
error.service.marketdata.position.details.null.error

I've taken this from Documentation:

Errors
Error responses contain a 4xx or 5xx HTTP status and a body with the following format:

{ "errorCode": "the error code" }

User errors caused by e.g. malformed json or invalid requests will be returned as HTTP 4xx errors. The suffix of error codes in validation failures can change depending on the request field that caused the failure, e.g. "invalid.request.forceOpen" indicates that the value on request field "forceOpen" was invalid.

The stated error is retrieved from this field and the documentation implies that and incorrect request was sent. This can not be the case as the API companion was used and the only fields filled out were "Deal Id", "Stop Level" and "Trailing stop". "Deal Id" and "Stop level" were valid and "Trailing stop" was set to false.

fptrader
same problem

I get the same problem - when I try to move a stop I get a null response and a bad request error

I am almost certain this used to work.

It does work when I use the compaion API

As you say there are only 2 fields to set - deal Id and trailingStop set to false;

fptrader
Can we get this fixed please.

Can we get this fixed please. Not being able to move a stop is a showstopper for me

kanm
I have the same issue. were

I have the same issue. were you able to fix it? thanks

Gianni
same issue in DEMO

Hello,

I have the same issue in DEMO enviromment, don't know yet in LIVE

for example today Oct,21th I opened via API a position and then I tried via API to edit the stop level:

at 19:24:07 I executed the request /positions/otc/DIAAAAC2D7T6SAP with
{"limitLevel":"26794.2","stopLevel":"26820.6","trailingStop":false,"trailingStopDistance":null,"trailingStopIncrement":null}

---> result: 404 {"errorCode":"error.service.marketdata.position.details.null.error"}

at 19:24:10 I executed the same exact request /positions/otc/DIAAAAC2D7T6SAP with
{"limitLevel":"26794.2","stopLevel":"26820.6","trailingStop":false,"trailingStopDistance":null,"trailingStopIncrement":null}

---> same result: 404 {"errorCode":"error.service.marketdata.position.details.null.error"}

at 19:24:26 I executed the same exact request /positions/otc/DIAAAAC2D7T6SAP with
{"limitLevel":"26794.2","stopLevel":"26820.6","trailingStop":false,"trailingStopDistance":null,"trailingStopIncrement":null}

but this time it worked!

---> result: 200 {"dealReference":"KD638NNVU8844TD"} and the position was updated

This behavior is quite weird as the same request sometimes works and sometimes does not

Do you have any advice too make it always working?

Thank you
Best regards
Gianni

Log in or register to post comments