/transfer

TRANSFER a release to another party.

Requires the sender to be the current owner.

In case you already fetched the pincode, you can no longer transfer the release.

The blockchain account address of the other party must be specified.

This must be one of your connections.*

Transfer a release

put

https://url:port/tmining/api/v1https://test-admin.securecontainerrelease.com:4430/legacy/tmining/api/v1

/releases/{address}/transfer

Transfer a release to another party. Requires the sender to be the current owner.

Authorizations

JWT

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

addressstringRequired

Body

application/json

addressstringOptional

Responses

202

Request accepted but not yet or partially processed

401

Invalid Authorization bearer token

403

Access forbidden

404

Release not found

409

Conflict error

500

Internal server error

put

/releases/{address}/transfer

HTTPcURLJavaScriptPython

PUT /tmining/api/v1/releases/{address}/transfer HTTP/1.1
Host: url:port
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 18

{
  "address": "text"
}

No content

---

EXAMPLE(S)

TRANSFER a release to an entity with an "address":

server = https://url:port/tmining/api/v1

TRANSFER a release to an entity with a "customer code":

server = https://url:port/tmining/api/v1