Skip to main content

Deploy Safe modules with a user signature

PATCH 
/api/v1/account/deploy-safe-modules

Takes an EIP-712 signature provided by the user's wallet and executes the account setup transaction. This is the second step in the account setup process, after obtaining the signature data from the GET /api/v1/account/signature-payload endpoint.

The process flow is:

  1. Call GET /api/v1/account/signature-payload to get the EIP-712 signature data
  2. Sign the data with the user's wallet
  3. Submit the signature to this endpoint to execute the transaction

This endpoint will wait for the transaction to be confirmed on-chain and return the transaction hash when successful. Because it waits for on-chain confirmation, this request may take up to 10 seconds to complete.

The setup process configures Safe account allowances and delay mechanisms required for secure operation.

Prerequisites:

  • User must have a deployed Safe account
  • The Safe account must have a currency set (via /api/v1/safe/set-currency)
  • User must have signed the data from GET /api/v1/account/signature-payload

Request​

Responses​

Successfully executed setup transaction