From d6dd6bb0b8c7738006a4e3b0c82acac75be3394d Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Tue, 18 Nov 2014 18:27:06 -0800 Subject: [PATCH] [DOC] rest max_fee uses XRP instead of drops now --- content/ripplerest_api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ripplerest_api.md b/content/ripplerest_api.md index 1bb256e6f0..63ed581f44 100644 --- a/content/ripplerest_api.md +++ b/content/ripplerest_api.md @@ -767,7 +767,7 @@ The JSON body of the request includes the following parameters: | client\_resource\_id | String | A unique identifier for this payment. You can generate one using the [`GET /v1/uuid`](#calculating_a_uuid) method. | | secret | String | A secret key for your Ripple account. This is either the master secret, or a regular secret, if your account has one configured. | | last\_ledger\_sequence | String | (Optional) A string representation of a ledger sequence number. If this parameter is not set, it defaults to the current ledger sequence plus an appropriate buffer. | -| max\_fee | String | (Optional) Optionally, the maximum transaction fee to allow. (As drops of XRP -- we should change this) If omitted, the server picks a static fee instead. | +| max\_fee | String | (Optional) Optionally, the maximum transaction fee to allow, as a decimal amount of XRP. If omitted, the server picks a static fee instead. | __DO NOT SUBMIT YOUR SECRET TO AN UNTRUSTED REST API SERVER__ -- The secret key can be used to send transactions from your account, including spending all the balances it holds. For the public server, only use test accounts.