tokens

Transfer a right (re-keying: new code issued, old code invalidated; no auth)

Only the current holder (who knows the current verificationCode) can transfer. A new code is issued and the old one is invalidated immediately. Paid transfers/auctions are not offered. Rate limited like verify. Subject to the location's policy: returns 409 with error policy_transfer_disabled when the location forbids transfers, or transfer_limit_reached when maxTransfers is exhausted.

post/api/rightos/tokens/{tokenId}/transfer

Request

  • Base URL: https://rightos.i-s3.com
  • URL: https://rightos.i-s3.com/api/rightos/tokens/{tokenId}/transfer
  • Auth: none required

Path parameters

tokenIdstring required

Request body

verificationCodestring required

Current code, proving transfer authority

Response

New code and wallet URL for the new holder (returned exactly once)

verificationCodestring

Returned exactly once. The server stores only its SHA-256 hash and cannot re-issue it.

walletUrlstring

Right Wallet URL (QR display) to hand to the end user.

Example response

{
  "token": {
    "id": "tok_2f8a1c9d3e4b5a6f7081",
    "title": "順番待ち / Queue ticket"
  },
  "verificationCode": "K7MP-Q2XT9",
  "walletUrl": "/software/rightos/wallet/tok_2f8a.../?code=K7MP-Q2XT9"
}

Changes

No recorded changes to this operation across all 1 revision of this API.