403 on fireblocks.freezeTransactionById(txId)

Developer Discussion
1

Hello, I’m integrating my app with Elliptic AML and am looking to use the freeze transaction API in situations where I want to quarantine a deposit based on the Elliptic response.

I’m using the JS fireblocks SDK (v5.33.0) and am calling the fireblocks.freezeTransactionById(txId) as described here. However, this returns a 403. Calling fireblocks.getTransactionById(txId) returns the transaction so my credentials are correct. Any ideas on how I can debug this further? The e.response.data from the error in my catch block doesn’t give me anything useful:

    "data": {
        "message": "ok",
        "code": 0
    },
2

Hi @Niros Can you please share the workspace name and the 4 first digits of the API key?

3

Thanks for the reply. I figured out what the problem is. I’m using my API Co-Signer which is assigned a “Signer” role. A “Non-Signing Admin” role is needed to freeze/unfreeze transactions per: https://support.fireblocks.io/hc/en-us/articles/360012832959-User-roles#h_01FPCQEKWTDQ33A2WES2NQ8GAF

4

Yap, that is correct.
I’m glad it worked out