Queue Transaction

POST /queue

Receives a signed SafeTx proposal from the client. The server hard-validates it (signature recovery against the recorded owner set, threshold arithmetic, nonce/hash consistency), mirrors it to the Safe Transaction Service — so it appears in app.safe.global at 1 of 2 — then runs analyzeRisk() inline.

Screening on:
- APPROVE (< 40): the agent confirms via the service and relays execTransaction
- REVIEW (40–70): queued for Telegram review, returns id and verdict
- BLOCK (> 70): rejected with alert — the pre-signed same-nonce cancel consumes the nonce
Screening off (screeningDisabled: true): queue-only — the server never analyzes, and the agent never signs. If the user signatures already meet the threshold, the client calls /execute (relay-only). Below threshold, the row waits for the backup key’s co-signature.

Proposals with screeningDisabled below the threshold are rejected outright for wallets whose own keys can never meet it (guarded wallets) — screening cannot be disabled there. Legacy v1 accounts without a backup key are exempt.

Request

{
  "id": "tx-1a2b3c4d",
  "txType": "safetx",
  "safeAddress": "0xYourSafeAddress",
  "safeTx": {
    "to": "0xRecipientOrToken",
    "value": "0",
    "data": "0x...",
    "operation": 0,
    "safeTxGas": "0",
    "baseGas": "0",
    "gasPrice": "0",
    "gasToken": "0x0000000000000000000000000000000000000000",
    "refundReceiver": "0x0000000000000000000000000000000000000000",
    "nonce": 7
  },
  "safeTxHash": "0x...",
  "safeNonce": 7,
  "proposedBy": "0xEmbeddedOwner",
  "userSignature": "0x...",
  "userSignatures": [{ "signer": "0xBackupOwner", "data": "0x..." }],
  "rejectionSignature": "0x...",
  "ownerAddresses": ["0xEmbedded", "0xBackup", "0xAgent"],
  "threshold": 2,
  "screeningDisabled": false,
  "to": "0xRecipientAddress",
  "token": "USDC",
  "amount": "100"
}

Field	Type	Required	Description
`id`	`string`	Yes	Client-generated transaction ID
`txType`	`string`	Yes	`"safetx"` for all user transactions
`safeAddress`	`string`	Yes	User’s Safe address
`safeTx`	`object`	Yes	The full SafeTx payload (EIP-712 message)
`safeTxHash`	`string`	Yes	EIP-712 hash — recomputed and verified server-side
`safeNonce`	`number`	Yes	Safe nonce (queue-tail, or current with force-execute)
`proposedBy`	`string`	Yes	Owner address the signature must recover to
`userSignature`	`string`	Yes	Proposer’s EIP-712 signature over `safeTxHash`
`userSignatures`	`array`	No	Additional co-signatures (each must recover to a distinct non-agent owner)
`rejectionSignature`	`string`	Yes	Proposer’s signature over the same-nonce empty cancel tx
`screeningDisabled`	`boolean`	No	Queue-only mode — requires user signatures to meet the threshold before execution
`token`, `amount`, `to`	`string`	No	Display metadata

Response

{
  "success": true,
  "id": "tx-1a2b3c4d",
  "risk": { "riskScore": 15, "verdict": "APPROVE", "reasons": [] }
}

Field	Description
`id`	Transaction ID in the queue
`risk`	Present when screening is on — score, verdict, reasons
`serviceWarning`	Present if the Safe Transaction Service mirror failed (queuing still succeeds)

API Reference

Queue

Execute

Invoices

Portfolio

Queue Transaction

POST /queue

Request

Response

​POST /queue

​Request

​Response

POST /queue

Request

Response