POST
/
vault
Create vault entry
curl --request POST \
  --url https://api.cloudcruise.com/vault \
  --header 'Content-Type: application/json' \
  --header 'cc-key: <api-key>' \
  --data '{
  "permissioned_user_id": "<string>",
  "user_name": "<string>",
  "password": "<string>",
  "domain": "<string>",
  "tfa_secret": "<string>",
  "user_alias": "<string>",
  "persist_session_storage": true,
  "persist_local_storage": true,
  "persist_cookies": true,
  "allow_multiple_sessions": true,
  "proxy": {
    "enable": true,
    "target_ip": "<string>"
  }
}'
{
  "permissioned_user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "user_name": "<string>",
  "password": "<string>",
  "domain": "<string>",
  "user_alias": "<string>",
  "tfa_secret": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "session_storage": {},
  "local_storage": {},
  "cookies": [
    {
      "name": "<string>",
      "value": "<string>",
      "domain": "<string>",
      "path": "<string>",
      "expirationDate": 123,
      "httpOnly": true,
      "hostOnly": true,
      "secure": true,
      "session": true,
      "storeId": "<string>",
      "sameSite": "<string>"
    }
  ],
  "persist_local_storage": true,
  "persist_cookies": true,
  "persist_session_storage": true,
  "allow_multiple_sessions": true
}

Authorizations

​
cc-key
string
header
required

API key-based authentication. Provide your CloudCruise API key in the cc-key header.

Body

application/json

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.

Response

Vault entry successfully created

Complete vault entry including system-generated fields