Authorizations
API key-based authentication. Provide your CloudCruise API key in the cc-key header.
Body
Comprehensive vault entry configuration for a user. Supports multiple authentication methods and persistence options to maintain user sessions across workflow executions. Credentials have to be encrypted with your own encryption key prior to sending to the API. Learn more about how to encrypt credentials here.
Unique identifier for referencing this vault entry in workflow executions
Primary encrypted username or email
Encrypted password credential
Target domain for vault entry credential
Two-factor authenticator secret key (TOTP)
A human readable identifier for the vault entry in the target system
Whether to maintain session storage across workflow executions
Whether to maintain local storage across workflow executions
Whether to maintain cookies across workflow executions
Controls whether the same set of credentials can be used simultaneously across multiple workflow executions. When set to true, multiple workflows can run in parallel using these credentials. When set to false or not specified, only one workflow can use these credentials at a time. We recommend keeping this as false (default) since some websites do not allow multiple active sessions for the same credentials and may invalidate existing sessions if a new one is detected.
Maximum number of concurrent sessions allowed when allow_multiple_sessions is true (null for unlimited)
Whether to prevent other sessions from starting while login is in progress
Session expiry interval from last activity using PostgreSQL interval format (e.g., "01:30:00" for 1.5 hours)
Session expiry interval from creation using PostgreSQL interval format (e.g., "7 days 00:00:00" for 7 days)
Two-factor authentication method:
- AUTHENTICATOR: Time-based one-time password using provided secret
- EMAIL: TFA codes sent to CloudCruise email (info+{user_id}+{domain}@cloudcruise.com)
- SMS: TFA codes sent to CloudCruise phone (+1 415 753-4639)
AUTHENTICATOR, EMAIL, SMS Controls whether to use a proxy during browser agent runs with these credentials. If target_ip is provided, we will assign a proxy closest to that IP.
Response
Vault entry successfully created
Complete vault entry including system-generated fields
System-generated unique identifier
Encrypted username
Encrypted password
Target domain for vault entry credentials
Human readable identifier
Two-factor authentication secret
Timestamp when the vault entry was created
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
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.
Two-factor authentication method
AUTHENTICATOR, EMAIL, SMS 
