[Feature Request] Archive Vault / Wallet *via* API

[cyrilchapon]

In a context where we abstract the wallet creation behind a REST API of our own; we have a use case where we probably should archive the vault account + wallet linked to a user.

I discovered it can be done via the console; but not via API.

Any plans to support it ?

[tomerrrrrr]

Hi @cyrilchapon ! Hiding the vaults from the UI is available via the hiddenOnUI property. https://developers.fireblocks.com/reference/post_vault-accounts-vaultaccountid-hide

[cyrilchapon]

From my tests, the "hidden" state is different from the archived one

[tomerrrrrr]

that is correct - we have 2 different things .. hiding , and archiving. You can see the comparison table of these two here - https://support.fireblocks.io/hc/en-us - and basically, if you plan on having more than 50 vault accounts, hiding is probably the better approach, which is why we focused on the hiding experience in our APIs. I would love to hear if you have more questions or benefits for the archiving approach over the hiding approach, that may work better with our APIs, and we can revisit this.

[cyrilchapon]

@tomerrrrrr ok thanks.

I would love to hear if you have more questions or benefits for the archiving approach over the hiding approach, that may work better with our APIs, and we can revisit this.

Well they're basically 2 separates use-case IMHO. The "hiding" approach is essentially here not-to-mess-the-ui with many-wallets applications (and I think we will need this eventually); while the "archiving" approach is sort of a "soft-delete" mecanism.

In other words :

• "Hiding" = "I'm using it, but it's not as crucial to show in the UI"
• "Archiving" = "I'm not using it anymore, and I don't want to see it — until I really need for special purposes"

[tomerrrrrr]

That is correct.
We are actually planning a soft-delete, but it will be a bit more grandiose :) will it be OK that I contact you as we progress with this initiative?

[cyrilchapon]

OFC, my pleasure ☺️
Looking forward