---
title: "Modify XRP account"
method: POST
path: "/v3/xrp/account/settings"
tags: ["Ripple (XRP) - Tatum API"]
---

# Modify XRP account

`POST /v3/xrp/account/settings`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/xrp/account/settings`
- Auth: API key in header `x-api-key`

/v3/xrp/account/settings

#### 10 credits per API call.

  

Modify XRP account settings. If an XRP account should be an issuer of the custom asset, this accounts should have rippling enabled to true. In order to support off-chain processing, required destination tag should be set on the account.  
  
This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key. No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production, [Tatum KMS](https://github.com/tatumio/tatum-kms) should be used for the highest security standards, and signatureId should be present in the request. Alternatively, using the Tatum client library for supported languages.

## Request body

- union
  - AccountSettingsXrpBlockchain
    - `fromAccount` string, required: XRP account address. Must be the one used for generating deposit tags.
    - `fromSecret` string, required: Secret for account. Secret, or signature Id must be present.
    - `fee` string: Fee to be paid, in XRP. If omitted, current fee will be calculated.
    - `rippling` boolean: Should be true, if an account is the issuer of assets.
    - `requireDestinationTag` boolean: Should be true, if an account should support off-chain processing.
  - AccountSettingsXrpBlockchainKMS
    - `fromAccount` string, required: XRP account address. Must be the one used for generating deposit tags.
    - `signatureId` string, uuid, required: Identifier of the private key associated in signing application. Secret or signature Id must be present.
    - `fee` string: Fee to be paid, in XRP. If omitted, current fee will be calculated.
    - `rippling` boolean: Should be true, if an account is the issuer of assets.
    - `requireDestinationTag` boolean: Should be true, if an account should support off-chain processing.

## Response `200`

OK

- union
  - TransactionHash
    - `txId` string, required: The hash (ID) of the transaction
  - SignatureId
    - `signatureId` string, uuid, required: The internal Tatum ID of the prepared transaction for Key Management Sysytem (KMS) to sign<br/>This is different from the <code>signatureId</code> parameter that you provided in the request body. The <code>signatureId</code> parameter in the request body specifies the signature ID associated with the private key in KMS.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403`: Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.
- `500`: Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.dev/tatum/apis/blockchain.md) - [All operations](https://skmtc.dev/tatum/apis/blockchain/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/blockchain/revisions/f9623a85f420?raw)