Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ripple Labs Orchestration payments API

Ripple Labs Orchestration payments API is one of 36 APIs that Ripple Labs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Orchestration payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 12 operations across 11 paths, and defines 20 schemas. It is described by OpenAPI 3.0.0, at version 2.0.

Requests are made against 2 base URLs: https://api.sandbox.palisade.co, https://api.palisade.co.

12 operations 11 paths 20 schemas 5 GET5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.0
Base URL
https://api.ripple.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Ripple Labs Orchestration payments API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (TokenAuth). By default, every request must be authenticated.

Paths & Operations 12

Across 11 paths, the API surfaces 12 operations — 5 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Orchestration payments 12
POST
/v4/orchestration/payment
Create orchestration payment
createOrchestrationPayment body → 201
GET
/v4/orchestration/payment
Get orchestration payments
getOrchestrationPayments 9 params → 200
GET
/v4/orchestration/payment/{uniqueReferenceNumber}
Get orchestration payment
getOrchestrationPayment 1 param → 200
POST
/v4/orchestration/payment/return
Return orchestration payment
returnOrchestrationPayment body → 201
POST
/v4/orchestration/payment/accept
Accept orchestration payment
acceptOrchestrationPayment body → 201
POST
/v4/orchestration/payment/reversal
Reverse orchestration payment
reverseOrchestrationPayment body → 201
GET
/v4/orchestration/payment/notification
Get orchestration notifications by status
getOrchestrationPaymentNotifications 6 params → 200
GET
/v4/orchestration/payment/notification/urn/{uniqueReferenceNumber}
Get orchestration notifications by unique reference number
getOrchestrationPaymentNotificationsByUniqueReferenceNumber 1 param → 200
GET
/v4/orchestration/payment/notification/{uuid}
Get orchestration notification
getOrchestrationPaymentNotificationByUUID 1 param → 200
PUT
/v4/orchestration/payment/notification/{uuid}/ack
Acknowledge orchestration notification
acknowledgeOrchestrationPaymentNotificationByUUID 1 param → 200
PUT
/v4/orchestration/payment/notification/ack
Acknowledge orchestration notifications
acknowledgeOrchestrationPaymentNotifications body → 200
POST
/v4/orchestration/payment/action
Post action to orchestration payment
sendOrchestrationPaymentAction body → 201

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are OrchestrationPaymentRequest (21 properties), OrchestrationPaymentResponse (18 properties), Page (8 properties), OrchestrationPaymentReturnRequest (8 properties). Each schema is shown below with its type and property counts.

Sort
object
6 properties
PaymentActionRequest
object
5 properties 3 required
ActivityOutput
object
Use this object when notificationtype is PARTNERSUBSTATE. For all other values of notificationtype, this property can be null.
3 properties
OrchestrationPayments
PaymentCustomRateRequest
object
Custom rate that the return payment quotes must use.
4 properties 4 required
NotificationUUIDList
object
JSON request object that represents a list of orchestration payment notification UUIDs to acknolwedge.
1 property
OrchestrationPaymentRequest
object
JSON request object that represents an orchestration payment.
21 properties 7 required
OrchestrationPaymentAcceptRequest
object
JSON request object that represents an orchestration payment accept request.
5 properties 3 required
OrchestrationPaymentReversalRequest
object
Use this JSON request object to reverse a payment.
3 properties 3 required
NotificationResponseRos
object
JSON request object that represents an orchestration payment notification.
7 properties
OrchestrationPaymentSubmitResponse
object
JSON response object that represents an orchestration payment query ID.
1 property
ActivityStatus
string
Activity status
NotificationAckResponse
object
Orchestration payment notification acknoledge response.
2 properties
PaymentReversalReasonRos
object
A structured object detailing reasons for a payment reversal.
2 properties 1 required
OrchestrationPaymentReturnRequest
object
Use this JSON request object to return a payment.
8 properties 2 required
OrchestrationPaymentResponse
object
JSON response object that represents an orchestration payment.
18 properties
NotificationList
array
List response of external notifications.
PaymentActionResponse
object
JSON response object that represents a payment action query ID.
1 property
ActivityError
object
Activity error object in JSON format.
3 properties
Page
object
Paginated response base object.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ripple-labs-orchestration-payments-api-openapi.yml Raw ↑

Other APIs Ripple Labs publishes across the network.

Ripple Labs Addresses API
Ripple Labs API Credentials API
Ripple Labs Auditing API
Ripple Labs Authentication API
Ripple Labs Balances and statements API
Ripple Labs Balances API
Ripple Labs Beneficiary confirmation API
Ripple Labs Counterparties API
Ripple Labs Diagnostics API
Ripple Labs Exchange transfers API
Ripple Labs Fees API
Ripple Labs Liquidations API