Transfer Owners

post

https://api.blockpeer.finance/api/blockpeer-trade/transfer/owners

File Upload Format (Base64 Data URI)

For endpoints that accept file inputs, files must be submitted as a Base64-encoded Data URI string in the document field.

Format
data:<mimeType>;name=<filename>;base64,<base64EncodedContent>

Example
json
{ "document": "data:application/octet-stream;name=BL-0xd7.tt;base64,ewogICJAY29udGV4dCI6IFsKICAgICJodHRwcz..." }

This API returns a URL with sessionId.
Use GET /auth/session-response?sessionId=<sessionId> to retrieve the session result.

Body Params

walletId

string

required

Identifier for the user's wallet that will authorize and sign the ownership transfer transaction.

holderAddress

string

The blockchain address that will become the new holder of the document after the transfer. Only one of holderAddress or holderDomain should be provided.

holderDomain

string

The domain that will become the new holder of the document after the transfer. Only one of holderAddress or holderDomain should be provided.

beneficiaryNomineeAddress

string

The blockchain address proposed as the new beneficiary for the document. Only one of beneficiaryNomineeAddress or beneficiaryNomineeDomain should be provided.

beneficiaryNomineeDomain

string

The domain proposed as the new beneficiary for the document. Only one of beneficiaryNomineeAddress or beneficiaryNomineeDomain should be provided.

remarks

string

Optional text remarks that will be encoded and embedded into the ownership transfer transaction.

document

file

required

Signed document file containing the metadata required to identify the associated token.

webhookUrl

string

Headers

Idempotency-Key

string

Unique key to ensure idempotency for API requests.

X-External-Id

string

Unique external ID for tracking purposes, can be used for debugging and analytics.

Responses

File Upload Format (Base64 Data URI)

200The ownership transfer operation has been initiated successfully. A redirect URL is returned, which must be opened by the user to complete authentication and signing of the transaction.

400The request is missing required fields, contains invalid data, or the authorization token was not provided.

401The caller is not authorized to perform the ownership transfer. This occurs when the caller is not recognized as the current beneficiary.

409The transfer request violates contract rules, such as nominating the current beneficiary or attempting transfer while a nominee is already set.

500Internal server error occurred during the ownership transfer initialization. This includes blockchain interaction failures, gas estimation errors, or unexpected runtime issues.