Create Orchestration
Creates a one-time orchestration that moves assets from a source profile to a destination. Use this endpoint when funds already reside on the Paxos platform and need to be transferred or converted as part of a single workflow.
A request to create an orchestration can fail with one of the following types of errors:
- Insufficient Funds
if the Profile (
profile_id) has insufficient available balance to fund the execution. - Already Exists
if an orchestration with the same external ID (
ref_id) has already been created.
Documentation Index
Fetch the complete documentation index at: https://paxos-0ac97319-mintlify-fix-orchestration-example-1774904789.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Paxos APIs use OAuth 2 with the client credentials grant flow.
Token URLs:
- Production: https://oauth.paxos.com/oauth2/token
- Sandbox: https://oauth.sandbox.paxos.com/oauth2/token
Learn more in the API credentials guide →
Body
A client or system-specified unique identifier for the orchestration - used for idempotency protection. Retries of a request should use the same ref_id to avoid duplicate transactions.
Response
A successful response.
Orchestrations can be created directly via the CreateOrchestration endpoint, or indirectly by an incoming deposit which matches an OrchestrationRule previously defined with the CreateOrchestrationRule endpoint.
A client or system-specified unique identifier for the orchestration - used for idempotency protection. Retries of a request should use the same ref_id to avoid duplicate transactions. For system-initiated orchestrations generated by invocation of an orchestration rule, the ref_id is generated the system.
TransferDetails refers to a specific Transfer and encodes its current status.
TransferDetails refers to a specific Transfer and encodes its current status.
Status represents the current state of an orchestration.
- PROCESSING: The orchestration is actively being processed.
- COMPLETED: The orchestration completed successfully.
- FAILED: The orchestration failed during processing.
- PENDING: The orchestration is awaiting approval before processing begins. Once approved, it transitions to PROCESSING. If rejected, it transitions to REJECTED.
- REJECTED: The orchestration was rejected during approval.
PROCESSING, COMPLETED, FAILED, PENDING, REJECTED The ID of the orchestration rule which triggered this orchestration. Can be empty for ad-hoc orchestrations.