Any Ideas please?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CodeFever
    Junior Member
    • Dec 2018
    • 14

    #1

    Any Ideas please?

    <LogEntry Date="2021-05-07 12:59:58" Severity="Info" Source="BetfairAPI.JsonRpcClient.Invoke" ThreadId="7">
    <Message>Request: SportsAPING/v1.0/listClearedOrders With args: {"betStatus":"SETTLED","eventTypeIds":[],"eventIds":[],"marketIds":[],"runnerIds":[],"betIds":[],"settledDateRange":{"from":"2021-05-07T11:17:39.52779Z","to":"2022-05-07T11:17:39.52779Z"},"groupBy":"BET","includeItemD escription":true,"locale":null,"fromRecord":0,"rec ordCount":0,"exId":0}</Message>
    </LogEntry>
    <LogEntry Date="2021-05-07 12:59:59" Severity="Info" Source="BetfairAPI.JsonRpcClient.Invoke" ThreadId="7">
    <Message>{
    "APINGException": {
    "requestUUID": "ie2-ang08a-prd-04270851-00182dffcb",
    "errorCode": "UNEXPECTED_ERROR",
    "errorDetails": ""
    },
    "exceptionname": "APINGException"
  • jabe
    Senior Member
    • Dec 2014
    • 705

    #2
    I can't see anything obvious. Have you tried it more than once? I wonder if losing the to-date might make a difference. Using a to-date a year in the future could be making it do unnecessary checks against future scheduled events. Or not. By the look of the documentation all the parameters with empty lists could be omitted, but that shouldn't matter.

    Comment

    • geoffw123
      Senior Member
      • Mar 2014
      • 250

      #3
      Hiya

      What is exld = 0 in your JSON request ? I cant spot that in the spec. Its plausible that an unknown param in the request could trigger the unexpected error response.

      Regards geoff

      Comment

      • CodeFever
        Junior Member
        • Dec 2018
        • 14

        #4
        Originally posted by geoffw123 View Post
        Hiya

        What is exld = 0 in your JSON request ? I cant spot that in the spec. Its plausible that an unknown param in the request could trigger the unexpected error response.

        Regards geoff
        Hi geof, my apologies for not replying before now but I am up to my eyes in these API error's, with emails 'flying' backwards and forwards to the development department. I have no idea as I am no programmer. Last September Betfair made changes to the way transaction charges were applied and this post relates to an earlier one regarding transaction charges levied to my account. The whole thing is stressing me out so much it's making me ill and this error is the least of my problems right now.

        Comment

        Working...
        X