# Storing Private Keys w Vaultwarden

**URL:** <https://vaultwarden.discourse.group/t/storing-private-keys-w-vaultwarden/4311>\
**Category:** Help\
**Created:** [January 14, 2025, 1:36pm UTC](https://vaultwarden.discourse.group/t/storing-private-keys-w-vaultwarden/4311 "2025-01-14T13:36:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ozpac](https://avatars.discourse-cdn.com/v4/letter/o/73ab20/32.png) [@ozpac](https://vaultwarden.discourse.group/u/ozpac)\
**Post date:** [January 16, 2025, 11:41am UTC](https://vaultwarden.discourse.group/t/storing-private-keys-w-vaultwarden/4311/2 "2025-01-16T11:41:20Z")

</div>

Is this thread of any help?

[https://vaultwarden.discourse.group/t/api-basics-how-to-pull-a-password](https://vaultwarden.discourse.group/t/api-basics-how-to-pull-a-password)

I think there is always a local client of some form in the current architecture as there aren’t any documented APIs for queuing the remote server.

---

_[View the full topic](https://vaultwarden.discourse.group/t/storing-private-keys-w-vaultwarden/4311)._