Articles in this section

Changelog for VALR API

  • Updated
Follow
23 June 2021
  • Added additional transaction types to transaction history.
    • VALR Pay PAYMENT transaction types including:  PAYMENT_SENT, PAYMENT_RECEIVED, PAYMENT_REVERSED and PAYMENT_REWARD;
    • Off-chain transaction types including: OFF_CHAIN_BLOCKCHAIN_WITHDRAW and OFF_CHAIN_BLOCKCHAIN_DEPOSIT;
    • Auto-buy AUTO_BUY transaction type.
08 February 2021
  • A Stop Limits API (/orders/stop/limit) is now available to place STOP_LOSS_LIMIT and TAKE_PROFIT_LIMIT orders.
  • Limit Orders (/orders/limit) POST request now accepts timeInForce as an optional parameter (GTC, FOK, IOC)
  • Time in Force (GTC, FOK, IOC) field is now included in GET responses of the following APIs: 
    • Open Order (/orders/open)
    • Order History (/orders/history)
    • Order Status (/orders/history/detail/*)
  • New order types of: STOP_LOSS_LIMIT and TAKE_PROFIT_LIMIT added to applicable Currency Pairs (currently BTCZAR, ETHZAR and XRPZAR) for the following Public APIs:
    • Public Order Types (/public/ordertypes)
    • Public Currency Pairs (/public/:currencyPair/ordertypes)\
  • Updated example for Public Currency pairs (/public/pairs) API with fields tickSize and baseDecimalPlaces for each traded currency pair.
  • Updated example for for all TransactionId API requests (/account/transactionhistory) with the id field in the response
  • Updated documentation for Trade History API (/account/:currencyPair/tradehistory)
  • Updated example for MarketData Trade History API (/marketdata/:currencyPair/tradehistory) with the quoteVolume field.
  •  
02 February 2021
  • The Order API (/orders/open) now includes the following fields in GET responses:
    updatedAt, status, type
  • Updated the Order History APIs (/orders/history) to include the feeCurrency field
  • Updated documentation: Updated the examples for Order History Detail APIs (/orders/history/detail/*) to include the fields:
    executedFee
    executedQuantity
    executedPrice
29 November 2020
  • Crypto withdrawals created (/wallet/crypto/:currencyCode/withdraw) with more decimals than the number of decimals supported by the currency will be truncated
  • The Currencies list (/public/currencies) now include the following new fields:
    • decimalPlaces
    • withdrawalDecimalPlaces
  • Withdrawal Info (/wallet/crypto/:currencyCode/withdraw) now includes the following new field:
    • withdrawalDecimalPlaces
  • Trade History for a currency pair (/account/:currencyPair/tradehistory) can now be filtered by the skip, limit, startTime, endTime and beforeId parameters. This is similar to Transaction History filtering.
6 September 2020
  • Asks & Bids on ZAR Orderbooks: The number of Asks and Bids sent via our Order Book APIs has been increased from 20 each to 40 each.
  • Order History Detail APIs (`/orders/history/detail/*`) now include the following new fields:
    • executedFee
    • executedQuantity
    • executedPrice`
12 July 2020
  • Rate limiting: Rate limit has been updated to 120 calls per 1 minute window. When rate limited, a response code of 429 and a response header of `x-valr-ratelimited: true` will be returned.
    • Example 1: You are allowed to do 120 calls from 10:10:00 to 10:10:59. When the time changes to 10:11:00, the counter will be reset and will start over.
    • Example 2: If the first request comes in at 10:10:30, the counter will be reset at 10:11:00
31 May 2020
  • Separated the API and Website web socket sessions. WebSockets which were connected via the API will no longer be closed when the user logs out of the VALR website.
  • When a `PING` message is received on the Trade WebSocket, a response with `NO_SUBSCRIPTIONS` in the `PONG` will be sent, if the user has not subscribed to any message types.
  • When a user connects and authenticates to the Account WebSocket, all account balances and open orders associated with the user account will be sent in the response. One `BALANCE_UPDATE` message for each asset held and one `OPEN_ORDERS_UPDATE` message containing all open orders on the account, across all order books will be sent.
  • The `BALANCE_UPDATE` web socket message now includes an `updatedAt` field.
  • The REST GET Balances response (`https://api.valr.com/v1/account/balances`) now includes an `updatedAt` field for each asset held.
  • Added the REST GET VALR Status (`https://api.valr.com/v1/public/status`) request which will indicate whether the API is "online" or in "read-only" mode. In "read-only" mode, only GET and OPTIONS requests are accepted. The "read-only" mode is sometimes necessary during maintenance.
  • The `filledPercentage` field on open orders is now accurate to two decimal places.
  • The REST GET Order Book (`https://api.valr.com/v1/marketdata/:currencyPair/orderbook`) response and the REST GET Order Book (Non aggregated) (`https://api.valr.com/v1/marketdata/:currencyPair/orderbook/full`) response now include a `LastChange` field, indicating the timestamp of the last update to the order book.
  • The `AGGREGATED_ORDERBOOK_UPDATE` message on the Trade web socket now includes a `LastChange` field, indicating the timestamp of the last update to the order book.
Please send any and all feedback via email to help@valr.com, we look forward to your comments and continuing to improve our product offering as we drive towards building VALR into a world class exchange.

Related articles