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/
The page number for paginated results. The value is zero-based, where 0 represents the first page.<br/> Set it to 0 to get the first page of results.
Filters for audit events where the range_field value is before this specified time stamp (not inclusive). You can also specify after to create a time range between after and before. If before is specified, range_field must also be specified.
Filters for audit events where the range_field value is after this specified time stamp (not inclusive). You can also specify before to create a time range between after and before. If after is specified, range_field must also be specified.
Filters payments before/after/between created and modified timestamps (CREATED_AT, MODIFIED_AT). For example, if you specify range_field=CREATED_AT, you would specify a timestamp (in the 24-character ISO 8601 YYYY-MM-DDTHH:mm:ss.sssZ format used in payment objects) as the value for before and/or after to fetch audit events before, after, or between the specified time range(s) (not inclusive). If range_field is specified, before and/or after must also be specified.
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/audit
https://[domainPrefix].ripplexcurrent.com/v4/audit
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/audit?page=0&size=10&before=string&after=string&range_field=string&actor=string&action=string&level=INFO&domain=USER_MANAGEMENT' \
-H 'Authorization: YOUR_API_KEY_HERE'Successful response
Sort details of this page
Message describing the audit event.
Information about the event, such as IP Address and URI.
Represents the audit event domain.
{ "first": true, "last": true, "number": 0, "numberOfElements": 0, "size": 0, "totalElements": 0, "totalPages": 0, "sort": [ { … } ], "content": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/audit/payment/{id}
https://[domainPrefix].ripplexcurrent.com/v4/audit/payment/{id}
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/audit/payment/{id}' \
-H 'Authorization: YOUR_API_KEY_HERE'Payment state change event trail.
Feature name associated with the entityId. Possible values are payment.
String representation of the action being taken, where DS = downstream and US = upstream in the messaging processing pipeline.
The RippleNetAddress of the originator of the message that triggered the creation of this event.
The type of message that was being processed that triggered the creation of this event.
[ { "featureName": "payment", "eventDetail": "Updated Payment to state PREPARED", "entityId": "d485f100-2af7-4e48-9ab1-3c7e28775691", "messageAction": "STATE_CHANGE", "createdAt": "2019-10-01T18:24:28.040000Z", "messageSender": "default", "messageType": "SETTLEMENT_PREPARE" } ]
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" }