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/
Name of the orchestration template. It must start with 'custom'.
The payment type for which the template is to be used.
The connector role for which the template is to be used.
Orchestration template description.
Activity order list.
Activity name.
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/config/template
curl -i -X POST \
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"name": "custom_orchestration_template_v1",
"payment_type": "REGULAR",
"connector_role": "SENDING",
"default_template": true,
"orchestration_template_description": "",
"activity_order": [
{
"activity_name": "activity_v1",
"next_activity": [
{
"status": "SUCCESS",
"activity_name": "activity_v1"
}
]
}
]
}'Successfully created orchestration template.
Orchestration template name.
The payment type for which the template is to be used.
The connector role for which the template is to be used.
Activity order list.
{ "name": "custom_orchestration_template_v1", "payment_type": "REGULAR", "connector_role": "SENDING", "default_template": true, "orchestration_template_description": "string", "activity_order": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/config/template
curl -i -X GET \
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template \
-H 'Authorization: YOUR_API_KEY_HERE'Successfully returned list of orchestration templates.
Orchestration template name.
The payment type for which the template is to be used.
The connector role for which the template is to be used.
Activity order list.
[ { "name": "custom_orchestration_template_v1", "payment_type": "REGULAR", "connector_role": "SENDING", "default_template": true, "orchestration_template_description": "string", "activity_order": [ … ] } ]
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template/{name}/
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/config/template/{name}/
curl -i -X GET \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template/{name}/' \
-H 'Authorization: YOUR_API_KEY_HERE'Successfully returned orchestration template.
Orchestration template name.
The payment type for which the template is to be used.
The connector role for which the template is to be used.
Activity order list.
{ "name": "custom_orchestration_template_v1", "payment_type": "REGULAR", "connector_role": "SENDING", "default_template": true, "orchestration_template_description": "string", "activity_order": [ { … } ] }
https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template/{name}/
https://[domainPrefix].ripplexcurrent.com/v4/v4/orchestration/config/template/{name}/
curl -i -X PUT \
'https://docs.ripple.com/_mock/products/payments-odl/api-docs/ripplenet/ripplenet/v4/orchestration/config/template/{name}/' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"default_template": true
}'Successfully created orchestration template.
Orchestration template name.
The payment type for which the template is to be used.
The connector role for which the template is to be used.
Activity order list.
{ "name": "custom_orchestration_template_v1", "payment_type": "REGULAR", "connector_role": "SENDING", "default_template": true, "orchestration_template_description": "string", "activity_order": [ { … } ] }
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" }