Safe Sets Jan. 19, 2027, Deadline to Migrate Queue Service APIs
Safe announced Safe Queue Service, a production service that uses one multichain API to process pending transactions, signatures, off-chain messages and delegate management.

Safe announced Safe Queue Service and set Jan. 19, 2027, as the deadline for developers to migrate from affected Transaction Service APIs covering transaction proposals, signature collection, off-chain messages and delegate management.
The production service uses a unified multichain API to process those items and is already used by Safe{Wallet}. A single request can retrieve pending transactions for as many as 100 Safe address-and-chain pairs. Each transaction proposal must include at least one valid signature.
Existing API keys remain usable. After the affected APIs close, Transaction Service will continue to provide executed transaction history, balances and Safe details.
Developers using the affected APIs must complete their migration by Jan. 19, 2027.