Transfer Management

Transfer

This endpoint initiates a token transfer on the blockchain between two wallets. The request body specifies the sender’s wallet address, the recipient’s wallet address, the token to be transferred, and the quantity. Upon successful processing, a transfer ID (id-in-client) is returned. This ID can be used to track the status of the transfer using the getTransferStatus endpoint. Note that while this endpoint initiates the transfer on the blockchain, confirmation may take some time depending on network conditions. If the idInClient already exists, a 409 error will be returned.

POST

transfers

curl --request POST \
  --url https://omnisafe.sandbox.ecrop.de/omni-safe/v1/transfers \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "id-in-client": "<string>",
  "tokenAddress": "<string>",
  "tokenMark": "<string>",
  "senderAddress": "<string>",
  "recipientAddress": "<string>",
  "quantity": 123
}'

"<string>"

Authorizations

Authorization

string

header

required

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

Body

application/json

Response

201

application/json

The created transfer transaction

The response is of type string.

Overview Transfer

curl --request POST \
  --url https://omnisafe.sandbox.ecrop.de/omni-safe/v1/transfers \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "id-in-client": "<string>",
  "tokenAddress": "<string>",
  "tokenMark": "<string>",
  "senderAddress": "<string>",
  "recipientAddress": "<string>",
  "quantity": 123
}'

"<string>"

OmniSafe product overview

Security

Integration

Authentication

Wallet Management

Token Management

Transfer Management

Signature Management

Transfer

Authorizations

Body

Response