Upcoming API changes for consistent data types

edited October 28

We plan to introduce a change to our current API that will ensure that the types of data we return from API requests match what is specified in the API documentation.

Currently, for some attributes like amounts, we return a string with a formatted amount even though the API documentation says we will return a number. After this change numbers that may be currently being returned in this format "1.00" will be returned as just 1.

Note that the display_value attributes, which are strings, will retain any formatting.

We plan to put this in place on the 27th of May 2019.

Here you can see before and after responses to a proposal request

Before

  "proposal": {
    "ask_price": "56.20",
    "date_start": "1555293474",
    "display_value": "56.20",
    "id": "a21619d5-69a1-f757-a9e4-54dbe60b00db",
    "longcode": "Win payout if Volatility 100 Index is strictly higher than entry spot plus 0.10 at 1 minute after contract start time.",
    "payout": "110",
    "spot": "7755.02",
    "spot_time": "1555293474"
  }

After

  "proposal": {
    "ask_price": 56.2,
    "date_start": 1555294111,
    "display_value": "56.20",
    "id": "13990e42-73ab-bfc4-24f2-321baf872da3",
    "longcode": "Win payout if Volatility 100 Index is strictly higher than entry spot plus 0.10 at 1 minute after contract start time.",
    "payout": 110,
    "spot": 7732.95,
    "spot_time": 1555294110
  }

This change is required to make our API more consistent and this change was implemented based on feedback from API developers.

Please check this discussion board periodically. We will keep you informed with the latest changes here.

Comments

  • Сhanges are already working? Will there be a transition period for debugging the code or will everything stop working on the 27th?

  • @wert said:
    Сhanges are already working? Will there be a transition period for debugging the code or will everything stop working on the 27th?

    The plan is for a hard cut over on the 27th. Note that this will just make values match the current API documentation.

  • Note that this change has now been delayed, we are now aiming to release this change on the Wednesday the 12th of June

  • We have now made it possible for you to start testing your applications against the new consistent version of API on Wednesday, June 12 until Monday, June 17 by contacting [email protected] and requesting details of the testing endpoint.

    If you have any questions, please contact us at [email protected] We’ll be happy to help.

  • Please Note that this has now been delayed until Monday the 17th, so testing will be able to be started on Monday the 17th through until Monday the 24th,

Sign In or Register to comment.