Record a request approved by signing it

The web app sends the transfer from the account’s own wallet through the normal flow, then posts the hash here: that report is both the approving vote and the execution receipt.

POST /api/v1/transfer_requests/{proposal_id}/approve

Record a request approved by signing it

cURL

curl --request POST \
  --url https://api.example.com/api/v1/transfer_requests/{proposal_id}/approve \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "txHash": "<string>"
}
'

200

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "requested",
  "txHash": "<string>",
  "transactionId": "<string>",
  "accountId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "appId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "requestedByUserId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "contactId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "quoteId": "<string>",
  "invoiceId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "amount": 123,
  "memo": "<string>",
  "requestedTime": "2023-11-07T05:31:56Z",
  "chatId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "approvalUrl": "<string>"
}

Authorizations

Authorization · string · header · required

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

Headers

x-api-key · string | null

Path Parameters

proposal_id · string<uuid> · required

Body

application/json

Body of the approve call.

The web app executes the transfer client-side through the normal send flow (funds leave the paying account's own wallet), then posts the resulting on-chain hash here. That report is both the approving vote and the execution receipt: the backend moves no money, it records what landed.

txHash · string · required

transactionId · string | null

Response

200

application/json

Successful Response

One outcome shape for both ways a transfer attempt can end.

Spent straight away: txHash only. Needs approval: the request that was filed, with the deep link to approve it. transactionId appears once an approved transfer has been reported back. A decline reason is not a field — it is a message in chatId, the request's thread.

id · string<uuid> | null

status · enum<string> | null

Client-facing status of a transfer_request proposal.

The record is a proposal (seven statuses); this is the short vocabulary the API keeps for the agent and the web app, mapped from ProposalStatus by :meth:from_proposal.

Available options: requested, approved, declined, failed

txHash · string | null

transactionId · string | null

accountId · string<uuid> | null

appId · string<uuid> | null

requestedByUserId · string<uuid> | null

contactId · string<uuid> | null

quoteId · string | null

invoiceId · string<uuid> | null

amount · number | null

memo · string | null

requestedTime · string<date-time> | null

chatId · string<uuid> | null

approvalUrl · string | null