New queue service, multichain by default
The Safe Queue Service brings pending transactions, signatures, messages, and delegates into one multichain API. Migrate before 19 January 2027.
PLATFORM TEAM, Safe Labs • 19 November 2026
)
The Safe Queue Service brings pending transactions, signatures, messages, and delegates into one multichain API.
Treasuries rarely live on one chain. A team might run Safes on Ethereum, Arbitrum, and Base, with signers in different time zones. Until now, seeing everything that was waiting for approval meant querying the Safe Transaction Service once per chain and combining the results yourself.
The Safe Queue Service removes that step. It's live in production, it already powers Safe{Wallet}, and it handles all pending offchain Safe data through one API: transaction proposals, signatures, offchain messages, and delegates.
The new service is a breaking change. The old endpoints are deprecated and will shut down on January 19 2027.
Read the migration guide to use the new service!
Migrate before 19 January 2027
If your integration proposes transactions, collects signatures, handles offchain messages, or manages delegates, it needs to migrate. The Transaction Service endpoints for pthose actions are deprecated, and Safe will remove them on 19 January 2027.
Most integrations will need to change the base URL, the request bodies, and the signing domain used for deletions and delegates. Your existing API keys work, and the Queue Service supports every network the Transaction Service supports. The migration guide maps each endpoint and field and ends with a checklist.
One view of everything waiting for approval
The Transaction Service has a separate endpoint for each chain. The Queue Service has one endpoint for all of them. A single request can return the pending queue for up to 100 Safe and chain pairs.
For treasury teams, that means one list of every transaction waiting for signatures, across every Safe and every network. For developers, it means fewer requests, no separate client per chain, and no merging results on the client. You pass each Safe with its chains, for example safes=0xA:1:137, and get one response back.
The queue only returns transactions that can still execute. The service automatically filters out anything below the Safe’s current nonce. You can also look up as many as 100 transactions by hash in a single call, which helps when you add notes and origin details to a history view.
Every proposal is signed
Every proposal sent to the Queue Service needs at least one valid signature from an owner, a delegate, or the owner of an owner Safe. The service rejects unsigned proposals. The service computes the transaction hash itself, identifies the proposer from the signature, and records how the proposer was authenticated.
As a result, the queue your team reviews holds only authenticated proposals, and every entry shows who proposed it.
Pending state that stays accurate
Removed signers drop out of the queue.
When an owner is removed from a Safe, their pending signatures and delegations are removed too. The queue never shows an approval from someone who is no longer a signer.
Reorgs are handled.
If a chain reorganization reverses an execution, the transaction goes back to pending.
Executed means closed.
The service rejects new signatures on transactions that have already been executed.
Built for how teams sign
Many signatures, one call
Submit up to 50 owner signatures in a single request.
Nested Safes
When a Safe is owned by another Safe, the parent Safe's transaction and the inner transaction can be proposed together. Signers of the owner Safe can propose directly.
Delegates that span chains
A delegation can apply to one Safe or to every Safe, and to one chain, or to every chain. Delegates can be renamed, and an owner can remove all of their delegates in one step.
Same keys, same networks
The Queue Service supports every network the Transaction Service supports, and your existing API keys work with it.
Executed history, balances, and Safe details stay on the Transaction Service. The rule is short: read pending data from the Queue Service and executed data from the Transaction Service.
The deprecated endpoints will be removed on 19 January 2027.
PLATFORM TEAM, Safe Labs • 19 November 2026