Skip to content
New release management

From version 1.13, the release management process is changing.

For more information, see Release management.

The latest platform version is: v1.15
The latest API version is: v1

Release history

The following table lists the most recent release versions, along with their release date, release type, and end of support date.

On-premise releases are fixed schedule releases for on-premise customers, with long-term support and a release cycle of six months. On-premise releases are synchronized with a specific SaaS release, and include the features of all the SaaS versions that were released since the previous on-premise release.

For example, on-premise customers who install version 1.15 also receive the features of versions 1.14 and 1.13.

For more information about release types, see Release management.

VersionRelease dateIntended forEnd of supportChangelog
1.15Sep. 27, 2024On-prem, SaaSSep. 27, 2025Ripple Custody 1.15
1.14Aug. 30, 2024SaaSOct. 14, 2024Ripple Custody 1.14
1.13July 31, 2024SaaSSep. 16, 2024Ripple Custody 1.13
1.12June 28, 2024On-prem, SaaSMar. 28, 2025Ripple Custody 1.12
1.11Feb. 23, 2024On-prem, SaaSDec. 27, 2024Ripple Custody 1.11

Previous releases

All of the releases listed in this table are all out of support. They are listed for information only.

VersionRelease dateEnd of supportChangelog
1.10Dec. 1st, 2023Sept. 27, 2024Harmonize 1.10
1.9July 31st, 2023May 1st 2024Harmonize 1.9
1.8Apr. 13th, 2023Jan. 31st 2024Harmonize 1.8
1.7Nov. 13rd, 2022Oct. 13th 2023Harmonize 1.7
1.6Sep. 12th, 2022May 13rd 2023Harmonize 1.6
1.5June 24th, 2022Mar. 12th, 2023Harmonize 1.5
1.4May 16th, 2022Sept. 12th, 2022Harmonize 1.4
1.3Mar. 4th, 2022Aug. 16th, 2022Harmonize 1.3
1.2Dec. 2nd, 2021Jun. 1st, 2022
1.1Nov. 10th, 2021Mar. 2nd, 2022
1.0Oct. 18th, 2021Jan. 10th, 2022

API deprecations and changes

The following list describes details of deprecated fields and significant updates to fields in each version of the API, along with the deletion date of any deprecations.

1.15

Deletion target: Sep. 27 2025

Transactions

  • In the following GET operations:

    • List transactions
    • Get transaction details

    The new field ledgerTransactionData.blockTime is deprecated. The approach to block date and time reporting will change in a future release.

Events

  • LIST: Events, of type ManifestCreated and ManifestUpdated:
    • New field accountId gives details of the account for which the manifest was created or updated.

1.14

Deletion target: Aug. 30th 2025

  • POST: Intent, of type v0_CreateTransactionOrder, for XRPL payments:

    • parameters.destination
    • parameters.destinationTag
    • parameters.amount

    are now deprecated in favor of fields in the new operations section created for tokens.

1.12

Deletion target: Jun. 28th 2025

Propose intent to create an account

  • POST: Intent, of type v0_CreateAccount: payload.ledgerId is deprecated in favor of payload.ledgerIds to support selection of specific ledgers in multi-ledger accounts.

1.10

Deletion target: Dec. 1st 2024

  • GET: Retrieve all generated addresses:
    • The address item details array (items.id, items.ledgerId, items.address, and so on) is now located inside the data array.

1.8

Deletion target: Apr. 13th 2024

Users

  • GET: List Users The filter roles has been renamed into roles[] and accepts now an array of strings directly. Multiple arrays can be combined together to realize an OR condition.

Accounts

  • GET: List accounts: additionalDetails.processingStatus is deprecated in favor of additionalDetails.ledgers.ledgerId and additionalDetails.ledgers.status. This is to support compatibility with multi-ledger accounts.
  • GET: Get account details: The properties lastBalancesUpdateRequestedAt and lastBalancesUpdateProcessedAt are now located inside the ledger array per each enabled ledger.
  • GET: Generate new account external address: This is now deprecated:
    • A new call under the same name is provided where the property ledgerId is now mandatory
  • GET: Retrieve latest external address: This is now deprecated. Use Retrieve all generated addresses with the new query parameter lastOnly. We have also provided new query parameter ledgerId and scope.

1.7

Deletion target: Nov. 13th 2023

Tickers

  • GET: id, ledgerId, name, kind, ledgerDetails, symbol, decimal fields are now deprecated:
    • data.* are now available instead

Intents

  • POST v0_CreateTicker intent:
    • We've introduced v0_ValidateTickers in this version, which allows you to create and validate multiple tickers at once

1.6

Deletion target: Sept. 12th 2023

Intents

  • POST v0_UpdateEndpoint: ledgerId field:
    • As it is not possible to update ledgerId value of an endpoint, we decided to deprecate this field.

Transfers

  • GET: Recipient address field:
    • Advanced address details are now available in addressDetails payload.
  • GET: Senders addresses field:
    • Advanced address details are now available in addressesDetails payload.

1.3

Deletion target: Mar. 4th 2023

Intents

  • GET: createdBy filter is now deprecated:
    • Use details.author.id and details.author.domainId instead
  • POST Approve: expiryAt field is now deprecated:
    • Intent approval and rejections can no longer expire. Use the intent proposal to set the intent expiration instead.
  • POST Reject: expiryAt field is now deprecated:
    • Intent approval and rejections can no longer expire. Use the intent proposal to set the intent expiration instead.

Transfers

  • GET: Bitcoin transfer metadata scriptPubKey and address fields:
    • Advanced Bitcoin transaction details are now available in the corresponding transaction's ledgerTransactionData.ledgerData payload, you can correlate the with the transfer output using the new outputIndex field on the Bitcoin transfer metadata.
  • GET: Transfer sender field
    • Use senders field instead. There can be 0, 1 or many senders for a transfer. The new array-based senders field covers all of these cases.

1.2

Deletion target: Dec. 2nd 2022

Intents

  • GET: intentTypes filter is now deprecated:
    • Use details.payload.type instead
  • GET: status filter is now deprecated::
    • Use state.status instead

Tickers

  • GET: typeInLedger filter is now deprecated:
    • Use kind instead

Transactions

  • GET: transactionOrderId filter is now deprecated:
    • Use orderReference.Id instead