New API: Not yet complete. Old API: About to vanish in a month

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mr Magoo
    Junior Member
    • Jan 2011
    • 86

    #1

    New API: Not yet complete. Old API: About to vanish in a month

    At some point, the new API will be completed and fully functional. (It isn't yet). In November, the old API will be turned off.

    So for how many days will the old and new API both be working, accessible and feature-complete? Will these two systems even overlap at all?

    Could Betfair care to comment about what 'overlap' time period they would consider acceptable to let their customers switch to the new API?
  • BetfairDeveloperProgram
    Administrator
    • Oct 2008
    • 679

    #2
    Api-ng

    Hi Mr Magoo,

    The outstanding Aus Wallet and transferFunds operations are in the process of being released today. API 6.0 will be retired on the 1st November 2014.

    If there are any other functions that are outstanding, which aren't listed as deprecated via https://api.developer.betfair.com/se...mparison+Table, please let us know.

    Kind Regards

    Neil

    Comment

    • betdynamics
      Junior Member
      • Sep 2010
      • 534

      #3
      Neil

      getAllCurrenciesV2 is still listed as To Be Added. Is a direct equivalent going to be released for API-NG and, if so, what is the likely date?

      Comment

      • BetfairDeveloperProgram
        Administrator
        • Oct 2008
        • 679

        #4
        Hi betdynamics,

        We have no plans to release a direct equivalent for getAllCurrenciesV2. Due to the low frequency of changes to the currency parameters (they haven't changed for several years), we have instead published this information in the API-NG documentation via https://api.developer.betfair.com/se...ncy+Parameters

        I have updated the API 6.0 v API-NG comparison table to make this clear.

        Thanks

        Neil

        Comment

        • betdynamics
          Junior Member
          • Sep 2010
          • 534

          #5
          Neil

          Thanks for the clarification.

          You already know my thoughts on this, but I'll restate them for the benefit of others.

          Personally I think that you should implement a direct replacement. By not making this data discoverable via the API, you are forcing bot makers into a position where the bot has to be physically altered every time you make a change to the currency tables.

          It really doesn't matter if this happens once a year or once every few years; at some point, someone's bets are going to stop being accepted (through no fault of their own) as the minimum stake/liability is adjusted.

          This seems to have been recognised in the old API, but deliberately excluded from the new API. It just seems somewhat shortsighted to me.

          Comment

          Working...
          X