Skip to main content

Release 15.07.2025

Orders and Transactions Schema Updates​

Enhancement: The Get Transaction by ID endpoint (GET /api/v1/orders/{orderId}/transactions/{transactionId}) response schema has been expanded:

  • The following properties are now required: primaryAmount, primaryBlockchain, secondaryAmount, serviceFeeAmount, and totalAmount.
  • The primaryBlockchain property has been added, providing explicit blockchain context for each transaction.
  • The primaryAmount, secondaryAmount, serviceFeeAmount, and totalAmount properties are now always present and non-nullable, ensuring consistent transaction data.

Enhancement: The Get Order by ID endpoint (GET /api/v1/orders/{orderId}) response schema has been refined:

  • The transactionsCount property has been removed from the required fields.
  • The transactions array items now allow the hash property to be nullable, improving compatibility with transactions that may not have a blockchain hash immediately available.

Error Response Format Changes​

warning

Breaking Change
The error response format for several endpoints has changed from an object to an array of error objects. Clients expecting the previous object format will need to update their error handling logic.

Change: The following endpoints now return an array of error objects (instead of a single object) in their 400 (Bad Request) responses:

  • Create payment (POST /api/v1/order/payment)
  • Create deposit (POST /api/v1/order/deposit)
  • Create refund (POST /api/v1/order/refund)
  • Create withdrawal (POST /api/v1/order/withdrawal)
  • Send crypto (POST /api/v1/order/send)
  • The code property is no longer required or present at the top level of the error response; instead, each error object within the array may contain a code.