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
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.
| Version | Release date | Intended for | End of support | Changelog |
|---|---|---|---|---|
| 1.15 | Sep. 27, 2024 | On-prem, SaaS | Sep. 27, 2025 | Ripple Custody 1.15 |
| 1.14 | Aug. 30, 2024 | SaaS | Oct. 14, 2024 | Ripple Custody 1.14 |
| 1.13 | July 31, 2024 | SaaS | Sep. 16, 2024 | Ripple Custody 1.13 |
| 1.12 | June 28, 2024 | On-prem, SaaS | Mar. 28, 2025 | Ripple Custody 1.12 |
| 1.11 | Feb. 23, 2024 | On-prem, SaaS | Dec. 27, 2024 | Ripple Custody 1.11 |
All of the releases listed in this table are all out of support. They are listed for information only.
| Version | Release date | End of support | Changelog |
|---|---|---|---|
| 1.10 | Dec. 1st, 2023 | Sept. 27, 2024 | Harmonize 1.10 |
| 1.9 | July 31st, 2023 | May 1st 2024 | Harmonize 1.9 |
| 1.8 | Apr. 13th, 2023 | Jan. 31st 2024 | Harmonize 1.8 |
| 1.7 | Nov. 13rd, 2022 | Oct. 13th 2023 | Harmonize 1.7 |
| 1.6 | Sep. 12th, 2022 | May 13rd 2023 | Harmonize 1.6 |
| 1.5 | June 24th, 2022 | Mar. 12th, 2023 | Harmonize 1.5 |
| 1.4 | May 16th, 2022 | Sept. 12th, 2022 | Harmonize 1.4 |
| 1.3 | Mar. 4th, 2022 | Aug. 16th, 2022 | Harmonize 1.3 |
| 1.2 | Dec. 2nd, 2021 | Jun. 1st, 2022 | |
| 1.1 | Nov. 10th, 2021 | Mar. 2nd, 2022 | |
| 1.0 | Oct. 18th, 2021 | Jan. 10th, 2022 |
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.
Deletion target: Sep. 27 2025
In the following GET operations:
- List transactions
- Get transaction details
The new field
ledgerTransactionData.blockTimeis deprecated. The approach to block date and time reporting will change in a future release.
- LIST: Events, of type
ManifestCreatedandManifestUpdated:- New field
accountIdgives details of the account for which the manifest was created or updated.
- New field
Deletion target: Aug. 30th 2025
POST: Intent, of type
v0_CreateTransactionOrder, for XRPL payments:parameters.destinationparameters.destinationTagparameters.amount
are now deprecated in favor of fields in the new
operationssection created for tokens.
Deletion target: Jun. 28th 2025
- POST: Intent, of type
v0_CreateAccount:payload.ledgerIdis deprecated in favor ofpayload.ledgerIdsto support selection of specific ledgers in multi-ledger accounts.
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 thedataarray.
- The address item details array (
Deletion target: Apr. 13th 2024
- GET: List Users The filter
roleshas been renamed intoroles[]and accepts now an array of strings directly. Multiple arrays can be combined together to realize an OR condition.
- GET: List accounts:
additionalDetails.processingStatusis deprecated in favor ofadditionalDetails.ledgers.ledgerIdandadditionalDetails.ledgers.status. This is to support compatibility with multi-ledger accounts. - GET: Get account details: The properties
lastBalancesUpdateRequestedAtandlastBalancesUpdateProcessedAtare now located inside theledgerarray 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
ledgerIdis now mandatory
- A new call under the same name is provided where the property
- 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 parameterledgerIdandscope.
Deletion target: Nov. 13th 2023
- GET:
id,ledgerId,name,kind,ledgerDetails,symbol,decimalfields are now deprecated:data.*are now available instead
- POST
v0_CreateTickerintent:- We've introduced
v0_ValidateTickersin this version, which allows you to create and validate multiple tickers at once
- We've introduced
Deletion target: Sept. 12th 2023
- POST
v0_UpdateEndpoint:ledgerIdfield:- As it is not possible to update
ledgerIdvalue of an endpoint, we decided to deprecate this field.
- As it is not possible to update
- GET: Recipient
addressfield:- Advanced address details are now available in
addressDetailspayload.
- Advanced address details are now available in
- GET: Senders
addressesfield:- Advanced address details are now available in
addressesDetailspayload.
- Advanced address details are now available in
Deletion target: Mar. 4th 2023
- GET:
createdByfilter is now deprecated:- Use
details.author.idanddetails.author.domainIdinstead
- Use
- POST Approve:
expiryAtfield is now deprecated:- Intent approval and rejections can no longer expire. Use the intent proposal to set the intent expiration instead.
- POST Reject:
expiryAtfield is now deprecated:- Intent approval and rejections can no longer expire. Use the intent proposal to set the intent expiration instead.
- GET: Bitcoin transfer metadata
scriptPubKeyandaddressfields:- Advanced Bitcoin transaction details are now available in the corresponding transaction's
ledgerTransactionData.ledgerDatapayload, you can correlate the with the transfer output using the newoutputIndexfield on the Bitcoin transfer metadata.
- Advanced Bitcoin transaction details are now available in the corresponding transaction's
- GET: Transfer
senderfield- Use
sendersfield instead. There can be 0, 1 or many senders for a transfer. The new array-basedsendersfield covers all of these cases.
- Use
Deletion target: Dec. 2nd 2022
- GET:
intentTypesfilter is now deprecated:- Use
details.payload.typeinstead
- Use
- GET:
statusfilter is now deprecated::- Use
state.statusinstead
- Use
- GET:
typeInLedgerfilter is now deprecated:- Use
kindinstead
- Use
- GET:
transactionOrderIdfilter is now deprecated:- Use
orderReference.Idinstead
- Use