API Co-signer Deployment Options and Installation Flow

This article outlines the available deployment options and the process for setting up a Co-signer to enable automatic transaction signing and approval of workspace configuration changes.

API Co-signer installation flow

After installing the Co-signer, configure the Policy to designate the API user paired with the Co-signer as the signer. This ensures that when a transaction meets the criteria defined in the policy, it will be automatically signed by the Co-signer that is paired to the specified API user.

Step 1: Setup and configure your deployment environment

Setup and configure the resources needed for the Co-signer to function within your environment. Additionally, configure your network and security services to allow access to the domains required for the Co-signer’s installation and operation.

Step 2: Add a new Co-signer to the workspace using an API user

Using the Fireblocks Console or APIs, create an API user and use it to add a new Co-signer to the workspace.

Step 3: Install and connect the Co-signer to the workspace

After preparing and configuring all necessary resources, download and run the installation script that matches your Co-signer type. Please select to deployment options below depending on which environment you have.