The RippleNet Server API provides you the ability to develop custom applications to manage or interact with your RippleNet instance.
Check out the best practices and tutorials.
The RippleNet Server API provides you the ability to develop custom applications to manage or interact with your RippleNet instance.
Check out the best practices and tutorials.
All API operations require a bearer access token for your target environment.<br>Learn how to request the access token.
The RippleNet Server API creates a dynamic [domainPrefix] that consists of {tenant}.{environment}.
Note: This example uses aperture as the tenant. Your tenant ID is different.
| Environment | Domaing Prefix | Domain | Base URL |
|---|---|---|---|
| Test | aperture.test | ripplexcurrent.com | https://aperture.test.ripplexcurrent.com |
| UAT | aperture.uat | ripplexcurrent.com | https://aperture.uat.ripplexcurrent.com |
| Production | aperture.prod | ripplexcurrent.com | https://aperture.prod.ripplexcurrent.com |
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/
https://[domainPrefix].ripplexcurrent.com/v4/
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/labels
https://[domainPrefix].ripplexcurrent.com/v4/payments/{payment_id}/labels
curl -i -X DELETE \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/labels?label=string' \
-H 'Authorization: YOUR_API_KEY_HERE'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/node-status
https://[domainPrefix].ripplexcurrent.com/v4/payments/{payment_id}/node-status
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/{payment_id}/node-status' \
-H 'Authorization: YOUR_API_KEY_HERE'Successfully retrieved payment states on each node participating in the payment.
Unique identifier of the payment.
State of the payment. This API only recognizes payments in the <code>LOCKED</code> state. For more on payment states, see Payment States in the RippleNet Developer Guide.<p></p>
RippleNet address of the participating node reporting the payment state.
Each node in the payment chain participates in sequence. Provides the order in the sequence in which this node participates.
[ { "paymentId": "efdf213c-9f64-43f7-80ab-15e7b4d139ae", "paymentState": "LOCKED", "nodeAddress": "rn.eur.uk.london", "pathOrder": 3 } ]
Returns a sanitized payment with sensitive content filtered from the user_info object. <p>Filtering user_info is customizable in rnn.properties. Content that is denylisted by default:</p> <p>/Cdtr, /CdtrAcct, /Dbtr, /DbtrAcct, /InitgPty, /InstForCdtrAgt, /Purp, /RgltryRptg, /RltdRmtInf, /RmtInf, /UltmtCdtr, /UltmtDbtr, /outbound_instructions/beneficiary_info</p>
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/filtered/{payment_id}
https://[domainPrefix].ripplexcurrent.com/v4/payments/filtered/{payment_id}
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/payments/filtered/{payment_id}' \
-H 'Authorization: YOUR_API_KEY_HERE'Successfully retrieved filtered payment.
Unique identifier of a payment.
Hash of all values in the Contract object used to ensure immutability. Once a payment transitions to the LOCKED state, the values in this object cannot change.
State of the payment. For details about payment states, see Payment States in the RippleNet Developer Guide.
Date and time at which the payment was last modified, as an ISO-8601 timestamp in UTC.
Represents all immutable parts of a payment agreed upon by all participants as a part of the Lock payment flow. Once a payment transitions to the LOCKED state, the values in this object cannot change.
ID that the sender can specify. Persisted on all RippleNet instances that participate in the payment.
Date and time at which this payment contract was created, as an ISO-8601 timestamp in UTC.
Date and time after which this payment contract expires, as an ISO-8601 timestamp in UTC.
JSON response object that represents a quote for a proposed payment or return payment.
Unique identifier for the quote.
Date and time at which the quote was created, as an ISO-8601 timestamp in UTC.
Date and time after which the quote and its pricing expire, as an ISO-8601 timestamp in UTC.
Indicates how the amount field should be treated for calculating quote values.
Indicates whether a quote's pricing is INDICATIVE or FIRM. An INDICATIVE quote allows for price movements between quote issuance and payment execution, such that the quoted amount and delivered amount may differ. A FIRM quote ensures that the quoted and delivered payment amounts are equal.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code that can be used to filter quotes at the opposite end of the quote request. For example, you can filter by this currency code to find the receiving currency for a quote with a SENDER_AMOUNT quote_type. If not sent in the request, this field value is set to null.
Transfer and exchange elements. A transfer element represents a movement of funds between two accounts. An exchange element represents the exchange of currencies between two accounts.
Unique identifier for the quote element.
Type of quote element.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order of each quote element along the liquidity path. If a quote includes five quote elements, each one is enacted according to its quote_element_order number to make the proposed payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Fees the sender is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Fees the receiver is charging. When quote_element_type is set to EXCHANGE, this field value is always set to 0.
Currency code of the sending amount. Included in quote elements with quote_element_type set to EXCHANGE.
Currency code of the receiving amount. Included in quote elements with quote_element_type set to EXCHANGE.
Triggered when a quote causes an account to go below its minimum_allowed_balance. Otherwise, this field value is set to null.
JSON object containing payment method metadata.
Details about the payout method.
Category of the payout method. Defaults to <code>OTHER</code> if not specified.
Itemized list of fees charged by each node.
Fees charged by each node participating in the payment.
Application-provided data explaining actions taken by RippleNet applications.
RippleNet address of the node from which the RippleNetInfo originated.
If applicable, provides an array of RippleNetInfoEntry's explaining transitions into the SETTLEMENT_DECLINED state
Information explaining the action taken by a RippleNet application. Could be a RippleNet error code, or a written explanation of the action taken
A Base64-encoded execution condition for this payment, the fulfillment of which will be presented to the validator to complete this payment. This value must match the execution_condition in the associated crypto transaction.
Unique identifier of the crypto transaction associated with this payment.
Address of the validator that validated the payment.
If the payment_type is RETURN, provides the payment ID of the original payment that this payment returns. Otherwise, this field value is set to null.
If the payment_type is REGULAR and the payment has an associated return payment, provides the payment ID of the return payment. Otherwise, this field value is set to null.
Represents the actual movement of funds in a payment. Each execution result corresponds to a quote element and represents its execution in a payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Represents the actual movement of funds in a payment as part of liquidation of a Wallet Receive payment.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Payment liquidation details
Reason behind failure of the liquidation, only applicable if the status is failure
Represents the movement of funds after an On-Demand Liquidity payment fails at intermediary transfer or destination exchange.
Unique identifier for this payment result.
Date and time at which this portion of the payment was executed, as an ISO-8601 timestamp in UTC.
Type of payment execution result.<p><ul> <li>TRANSFER represents the movement of funds between two accounts.</li> <li>EXCHANGE represents the exchange of currencies between two accounts.</li> <li>EXCHANGE_TRADE represents the exchange of fiat to digital currency on a digital exchange.</li> <li>CRYPTO_TRANSFER represents the movement of digital funds between two digital exchanges.</li> </ul></p>
Order in which the payment execution action was taken along the liquidity path. For example, a payment may include five execution results along the liquidity path. Each execution result has an order number that indicates the order in which the execution result was achieved to make the payment.
RippleNet account name and address of the sender, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
RippleNet account name and address of the receiver, in the format accountname@ripplenetaddress. For example, new_york@rn.us.ny.new_york.
Currency code of the sending amount. Included in execution results with execution_result_type set to EXCHANGE.
Currency of the receiving amount. Included in execution results with execution_result_type set to EXCHANGE.
The details of an FX Rate for a quote or payment.
Currency of the transfer. Returned in execution results with execute_result_type set to TRANSFER.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool. (Soon to be deprecated)
Configuration of the incentive pool on the xRapid side. Two values are supported, firm and fx. For firm, xRapid guarantees that the FX rate at the moment of execution is the same as at the moment of quoting. For fx, xRapid guaratees a predefined FX rate.
Amount of XRP representing the difference in FX rate between the moment of quoting and the moment of execution. A positive value is the amount taken out of the incentive pool. A negative value is the amount returned to the incentive pool.
Hash representing the unique identifier for the transfer of funds in the XRP ledger.
The id from an exchange associated with a transaction involving an exchange account.
Represents the delta between quoted and received executed amounts, for exchange trades.
Collection of user-provided data whose keys are filtered based on a configurable denylist.
RippleNet address of the node that provided the user information.
User information optionally provided when accepting the payment.
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when locking the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when declining to lock the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying acceptance of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when retrying settlement of the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settling the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when settlement for the payment is declined. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when failing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
Payment sub-state information provided using sub_state and memo fields when finalizing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
User information optionally provided when completing the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, user information optionally provided when forwarding the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
If applicable, information optionally provided using return_reasons when returning the payment. For more information, see [User Info Entry Object][user-info-entry].
User information provided across the payment lifecycle stored as arbitrary JSON key/value pairs.
Date and time at which the user information was added to the payment, as an ISO-8601 timestamp in UTC.
{ "payment_id": "d485f100-2af7-4e48-9ab1-3c7e28775691", "contract_hash": "ccb23bd87f13cc13b9d616a9723f76e112aeac8628b2082e0f8bf3b8c670b103", "payment_state": "COMPLETED", "modified_at": "2019-10-01T18:25:47.347Z", "contract": { "sender_end_to_end_id": "string", "created_at": "2019-10-01T18:18:13.665Z", "expires_at": "2019-10-01T18:55:22.824Z", "quote": { … }, "fee_info": { … } }, "ripplenet_info": [ { … } ], "execution_condition": "PrefixSha256Condition{subtypes=[ED25519-SHA-256], type=PREFIX-SHA-256, fingerprint=sfGGHCrkyaMsLQNB62w_4zarlPChHKm47JkXVQbs1z0, cost=132360}", "crypto_transaction_id": "4e05da26-7872-4a1f-b9b7-db7604757c37", "validator": "rn.us.ca.san_francisco", "payment_type": "REGULAR", "returns_payment_with_id": "a69b322f-faa4-4531-bcff-897e5839c130", "returned_by_payment_with_id": "c929a87b-81b8-4878-b21c-1aeaa4fe9276", "execution_results": [ { … } ], "liquidation_execution_results": [ { … } ], "liquidation_details": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "string", "failure_reason": "string", "failure_count": 0 }, "push_forward_execution_results": [ { … } ], "user_info": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/info
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/info
curl -i -X GET \
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/info \
-H 'Authorization: YOUR_API_KEY_HERE'{ "name": "Integration Module", "version": "1.2.0" }