Skip to content

OfferResponseTransferWithdraw.md

Latest commit

 

History

History
22 lines (10 loc) · 1.26 KB

OfferResponseTransferWithdraw.md

File metadata and controls

22 lines (10 loc) · 1.26 KB
Raw

OfferResponseTransferWithdraw

Withdraw your own OUTGOING transfer offer. Carries no arguments — offerId in the path is the offer, so the vault account and blockchain are resolved from it rather than restated. Was CantonCallType.TRANSFER_WITHDRAW with a 3-field payload until FA-10624.

Properties

Name Type Description Notes
responseType ResponseTypeEnum How you are answering the offer. Must be one of the values listed in the transaction's `cantonDetails.offerResponse.availableResponses` — TOP-LEVEL on the transaction, not nested under an `additionalInfo` envelope, which does not exist on `TransactionResponse`. `availableResponses` states what this offer TYPE accepts. It is set when the offer arrives and does not change, so it does NOT tell you whether the offer is still answerable — check `expiresAt` and the transaction's status for that, and expect this endpoint to be the authority: it re-checks state and expiry on every call and answers 409 when either has moved.

Enum: ResponseTypeEnum

Name Value
TRANSFER_WITHDRAW "TRANSFER_WITHDRAW"