Transfer Management

Transfer

Retrieves the status of a previously initiated token transfer on the blockchain. To use this endpoint, you’ll need the idInClient that was returned by the transfer endpoint when the transfer was initiated. This idInClient allows you to track a specific transfer. The response includes the blockchain transaction hash (if the transfer has been confirmed), the current status of the transfer (e.g., “PENDING”, “DONE”, “FAILED”), and any error messages encountered.

GET

transfers

{id-in-client}

curl --request GET \
  --url https://omnisafe.sandbox.ecrop.de/omni-safe/v1/transfers/{id-in-client} \
  --header 'Authorization: Bearer <token>'

[
  {
    "transactionHash": "<string>",
    "status": "SENDING_TO_BLOCKCHAIN_BESU",
    "errorMessage": "<string>"
  }
]

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id-in-client

string

required

The client-provided ID of the transfer.

Response

200

application/json

Last blockchain block

transactionHash

string

The hash of the transaction on the blockchain.

status

enum<string>

The current status of the transfer.

Available options:

SENDING_TO_BLOCKCHAIN_BESU,

SENDING_TO_BLOCKCHAIN_GETH,

DONE,

FAILED

errorMessage

string

An error message if the transfer failed.

Transfer Overview

curl --request GET \
  --url https://omnisafe.sandbox.ecrop.de/omni-safe/v1/transfers/{id-in-client} \
  --header 'Authorization: Bearer <token>'

[
  {
    "transactionHash": "<string>",
    "status": "SENDING_TO_BLOCKCHAIN_BESU",
    "errorMessage": "<string>"
  }
]

OmniSafe product overview

Security

Integration

Authentication

Wallet Management

Token Management

Transfer Management

Signature Management

Transfer

Authorizations

Path Parameters

Response