Issue description

This error message indicates that the workspace Owner still needs to approve the API user's MPC key shares.

Resolution

Check the Owner's device for pending MPC key share approval notifications.

If the notification is less than 12 hours old, the Owner can still approve the key shares and the API user will be ready to sign transactions. Once the owner approves your new MPC keys on their Fireblocks mobile app, you have 6 hours to complete the MPC registration.
If the Owner is unable to approve the request due to Error 52, deny the pending request and submit a request to Fireblocks Support.
If there is no notification or another error, re-enroll the API user and then pair it with the API Co-Signer again to resend the approval request.

If you have a question or need assistance, submit a request to Fireblocks Support and include the following information in your request:

Workspace name
The first four characters of the corresponding API key
User information (indicate whether the user is an active Co-Signer or is going through initial setup)

Additionally, copy the following logs from the API Co-Signer:

Transaction handling (/databases/cosigner/log/customer_cosigner.log)
- Transaction signing flow
- Logging the Callback Handler request and response
Configuration changes to the API Co-Signer (date_time.run.log)
- Setup
- Pairing a new API user
- Changing the Callback Handler URL