Retrieves vault entries for users matching the specified criteria.
Note:
- If the query parameters are omitted, all vault entries will be returned.
- If both parameters are provided, the response will be a single vault entry record (not a list).
API key-based authentication. Provide your CloudCruise API key in the cc-key header.
Unique identifier for the vault entry. Optional, but if provided, 'domain' must also be provided.
Target domain to filter vault entries. Optional, but if provided, 'permissioned_user_id' must also be provided.
Vault entries successfully retrieved.
Complete vault entry including system-generated fields
System-generated unique identifier for the vault entry
Unique identifier for referencing this vault entry in workflow executions
Encrypted username
Encrypted password
Target domain for vault entry credentials
Human readable identifier
Two-factor authenticator secret key (TOTP). Required when tfa_method is AUTHENTICATOR. This should be encrypted with your encryption key prior to sending to the API, similar to other credentials. The secret is typically provided in base32 format from authenticator apps.
Two-factor authentication method
AUTHENTICATOR, EMAIL, SMS Computed email address for TFA codes when tfa_method is EMAIL. This is automatically generated by CloudCruise in the format: info+{user_id}+{domain}@cloudcruise.com This field is read-only and cannot be set via the API.
Computed phone number for TFA codes when tfa_method is SMS. This is automatically determined based on workspace configuration or defaults to CloudCruise's default phone number. This field is read-only and cannot be set via the API.
The workspace this vault entry belongs to
The user who created this vault entry
Timestamp when the vault entry was created
Timestamp when the vault entry was last updated
Session storage data
Local storage data
Active vault entry cookies
Whether to maintain local storage across sessions
Whether to maintain cookies across sessions
Whether to maintain session storage across sessions
Specific domain to use when storing cookies
Whether to allow multiple concurrent sessions
Maximum number of concurrent sessions allowed (null for unlimited)
Whether to prevent other sessions from starting while login is in progress
Session expiry interval from last activity (e.g., "01:30:00" for 1.5 hours). Set to null for no expiry from last use.
Session expiry interval from creation (e.g., "7 days 00:00:00" for 7 days). Set to null for no expiry from session data set.
Computed timestamp when the session data expires based on expiry settings
Timestamp when the session data (cookies, storage) was last set
Legacy field for target IP address (deprecated, use proxy.target_ip instead)
Geographic location associated with this vault entry
The assigned proxy connection string for this vault entry. This is automatically assigned based on the proxy configuration provided when creating/updating the entry. Format: ip:port (e.g., "91.124.2.237:61234")