INVALID_INPUT_DATA market id passed is invalid

[Trollkarl]

Hi,

I am experiencing a problem where I make a call to the JSON RPC placeOrders endpoint. I make a request and get back an error:

{"jsonrpc":"2.0","error":{"code":-32099,"message":"ANGX-0002","data":{"APINGException":{"requestUUID":"ie2-ang26b-prd-05190827-005b2b5914","errorCode":"INVALID_INPUT_DATA","erro rDetails":"market id passed is invalid"},"exceptionname":"APINGException"}},"id": 5}

In the above case the market ID was 1.171350945, I have recorded the exact JSON I sent to the server and if I try it later the exact same request works, so I am confident that the market ID and the rest of the request is indeed correct.

I wonder if it's related to the market lifecycle, is it possible that a market opens but then quickly suspends?

I have further requestUUIDs as examples if BDP can provide some assistance.

[geoffw123]

Hi

Why post the Json data for the reply ? INVALID_INPUT_DATA would have sufficed for that. Please post the json data you sent, someone might be able to spot the error if they can see the exact Json that went down the wire .

[Trollkarl]

Here's the request JSON:

[{
"jsonrpc":"2.0",
"method":"SportsAPING/v1.0/placeOrders",
"id":5,
"params":{
"marketId":"1.171350945",
"customerStrategyRef":"q",
"instructions":[
{
"orderType":"LIMIT",
"side":"BACK",
"limitOrder":{
"price":2.2,
"size":2.0,
"persistenceType":"PERSIST"
},
"selectionId":26111239
},
{
"orderType":"LIMIT",
"side":"BACK",
"limitOrder":{
"price":2.2,
"size":2.0,
"persistenceType":"PERSIST"
},
"selectionId":8223214
}
]
}
}]

As I say I am very confident the request is request, when I sent it again manually it worked.

[jabe]

Don't know. The request looks fine. One for support.

[geoffw123]

Looks OK to me too, the only thing i noticed that is maybe different to mine is the outer enclosing square brackets, I dont think mine sends those, but you have said it worked when you try same data again. Brackets are maybe optional thing. It shouldnt be related to market suspension as that is a different error response not INVALID_INPUT_DATA.
Maybe itt was just a one off giitch where the sent packet got corrupted somehow before it reached BF.

[RogerMoore]

I'm getting the same issue, some requests work, others don't.. requests seem fine in isolation if retried.

[RogerMoore]

Mine was the customerRef including forbidden char/exceeding length (32) in conjunction with using the `betfair-ts` npm package which for some reason decides to obfuscate the useful error description in the response... now fixed