POST
/
v2
/
orchestration
/
orchestrations
{
  "id": "<string>",
  "profile_id": "<string>",
  "identity_id": "<string>",
  "account_id": "<string>",
  "customer_id": "<string>",
  "ref_id": "<string>",
  "source_asset": "<string>",
  "destination_asset": "<string>",
  "source_amount": "<string>",
  "source_transfer": {
    "transfer_id": "<string>",
    "status": "PENDING"
  },
  "destination_transfer": {
    "transfer_id": "<string>",
    "status": "PENDING"
  },
  "status": "PROCESSING",
  "fail_reason": {
    "detail": "<string>"
  },
  "source": {
    "crypto": {
      "address_id": "<string>",
      "address": "<string>",
      "network": "<string>"
    },
    "fiat": {
      "deposit_instructions_id": "<string>",
      "memo": "<string>"
    },
    "profile": {
      "profile_id": "<string>"
    }
  },
  "destination": {
    "crypto": {
      "address": "<string>",
      "network": "<string>"
    },
    "fiat": {
      "bank_account_id": "<string>",
      "memo": "<string>"
    },
    "profile": {
      "profile_id": "<string>"
    }
  },
  "orchestration_rule_id": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "metadata": {}
}

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json

Response

200 - application/json

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.