Intermittent ANGX-0006 Errors

[winterwooksie]

Throughout the day i intermittently get unexpected errors from the API, usually when calling listMarketBook. Here is a sample request and response

{"jsonrpc":"2.0","method":"SportsAPING/v1.0/listMarketBook","params":{"locale":"en","currencyC ode":"GBP","marketIds":["1.183843590"],"priceProjection":{"priceData":["EX_ALL_OFFERS","SP_AVAILABLE"],"exBestOffersOverrides":null,"virtualise":"fal se" },"orderProjection":"ALL","matchProjection":"NO_ RO LLUP"},"id":1}

{"jsonrpc":"2.0","error":{"code":-32099,"message":"ANGX-0006","data":{"APINGException":{"requestUUID":"ie2-ang24b-prd-05120754-001db60937","errorCode":"UNEXPECTED_ERROR","errorD etails":""},"exceptionname":"APINGException"}},"id ":1}

Does anybody else get this occasionally ?

I assume someone from the API Team (Neil?) could use the requestUUID to look at the trace to see what causes the problem. Interested to know what the cause is !

[jabe]

There are some amendments that I think could help.

If you want to use the default for something, omit the parameter completely, if possible.

FALSE should be in capitals and it is a Boolean value in itself. It shouldn't be in quotes. This may be what's upsetting the API.

You didn't specify EX_BEST_OFFERS, so no need to specify exBestOffersOverrides. I'm not convinced that null is a value that would even work for that.

[winterwooksie]

Thanks jabe - I'll try those suggestions, however, I can't make a case for why this would be intermittent.. ? The failure rate is probably less than 0.5% of calls I make, the vast majority succeed with no problems.