API Co-signer Management
In addition to manual transaction signing and Workspace configuration approvals using a mobile device, you can automate signing and approvals with an API Co-signer. This is ideal for workspaces that handle high transaction volumes or frequent activity.
A Co-signer is connected to a workspace by pairing it with an API user. These user roles can be paired with a Co-signer: Admin, Non-Signing Admin, Signer, Approver. If the paired API user is a Signer or an Admin, you will be asked to approve MPC key shares for that user, because only those two roles hold MPC key shares and can sign. A Non-Signing Admin or Approver is paired to automate approvals and does not require MPC key share approval.
To activate automatic signing through the Co-signer, configure the Policy to designate the API user paired with the Co-signer as the signer. When a transaction you initiate meets the criteria defined in the policy, it will be automatically signed by the Co-signer associated with the configured API user.
At that point, you can add multiple API users to the Co-signer and configure the Callback Handler for each API user paired with it.
Use the articles below for detailed guides and information.