Expand description
The Vaultwarden wire shapes the connector reads and writes.
Ciphers cross as serde_json::Value, not as a lossy typed struct: an update
must send the whole object back, and a typed shape that dropped the TOTP
seed, a passkey or a field this version does not model would delete it on
the server. The facade decrypts the fields it needs from the value; the
connector only moves it.
Re-exports§
use serde::de::Deserializer;🔒use serde::de::IgnoredAny;🔒use serde::de::MapAccess;🔒use serde::de::Visitor;🔒use serde::Deserialize;🔒use serde::Deserialize;🔒use serde::Serialize;🔒use serde::Serialize;🔒use zeroize::Zeroize;🔒use zeroize::Zeroize;🔒use zeroize::Zeroizing;🔒
Structs§
- Attachment
Meta - One attachment’s metadata, as a cipher and the download route carry it.
- Folder
- One folder. Folders are simple enough to type: an update sends only the name.
- Folder
List - The
GET /api/folderslist envelope. Vaultwarden sends every folder indatawith a nullcontinuationToken, and no server this family talks to pages, so the token is not modelled. - Organization
- One organization’s wrapped key, as the profile carries it.
- Prelogin
- The prelogin answer: which KDF the account uses and its parameters.
- Profile
- The account profile inside
GET /api/sync. - Sync
Data - The parts of
GET /api/syncthis family reads. - Token
Response - The token endpoint’s answer for both the password and refresh grants.
- TwoFactor
Code - The second factor a password grant carries, when the account asks for one.
Functions§
- size_
from_ 🔒number_ or_ string - Read an attachment size that arrives as either a JSON number or a string.