Data protection functions provide encryption and secure transmission options to strengthen project security levels.Documentation Index
Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt
Use this file to discover all available pages before exploring further.
Safe data transmission and storage are supported through liveform encryption settings and secure transmission settings.
Liveform Encryption Settings
You can maintain higher security levels for user submissions through liveform encryption settings.
Encryption Algorithm Selection
When encryption is needed in liveform URL’s Query String, data must be encrypted using the selected encryption algorithm and encryption key.| Algorithm | Description |
|---|---|
| ECB (Electronic Codebook) | Fast and simple block encryption method |
| GCM (Galois/Counter Mode) | Enhanced encryption method including authentication and integrity functions |
encrypted={encrypted_data}.Encryption-only Mode
Activate encryption-only mode when you want to encrypt and use all Query String parameters.
pid, encrypted, lang parameters are allowed in liveform URL, and all other parameters must be encrypted and included in the encrypted parameter.
Allowed URL Format:
Encryption Key Management
Manages keys to be used for encryption. You can use API KEY or issue and use a dedicated key (secretKey).

| Key Type | Description |
|---|---|
| API KEY | Use the default API key assigned to the project as encryption key |
| Dedicated Key (secretKey) | Dedicated encryption key newly issued and used in liveform |
How to Use Liveform URL Encryption
Learn how to encrypt and use Query String parameters in liveform URLs.Step 1: Prepare Data to Encrypt
Prepare Query String parameters to encrypt in JSON format.pid, lang query strings and sid, action query strings used in ‘Additional Process (Injection)’ page do not support encryption. However, when using Injection, sid and action must be encrypted by including them inside the encrypted parameter.Step 2: Perform Encryption
Encrypt data using the selected encryption algorithm (ECB or GCM) and encryption key (API KEY or secretKey).Encryption Guide
Step 3: Add Encrypted Data to URL
Add encrypted data to theencrypted query parameter.
Secure Transmission Settings
Settings to strengthen security for data transmission via API methods.
Secure Data Transmission
When secure data transmission option is activated, all data transmission between ARGOS and customers is encrypted.| Setting | Description |
|---|---|
| Secure Data Transmission | Encrypts and transmits data in API methods (GET, POST, PATCH, etc.) and webhooks. |
API Request Data Encryption
When secure data transmission is activated, Request Body must be encrypted when making API requests. Encryption Methods:- API Requests (GET, POST, PATCH): AES-256-ECB method
- Webhook Data: AES-256-CBC method
API Response Data Decryption
When secure data transmission is activated, API responses are also encrypted, so decryption is required. Response Format:Webhook Data Encryption/Decryption
Webhook data is encrypted using AES-256-CBC method.Encryption Guide
Configuration Guide by Scenario
Scenario 1: Selective Encryption Usage
Scenario 1: Selective Encryption Usage
- Encryption Algorithm: Select ECB or GCM
- Encryption Key: Select API KEY or dedicated key
- Encryption-only Mode: Deactivated
email is a normal parameter, and sensitive information such as token is encrypted and included in the encrypted parameter.Scenario 2: Full Encryption Usage (Encryption-only Mode)
Scenario 2: Full Encryption Usage (Encryption-only Mode)
- Encryption Algorithm: Select ECB or GCM
- Encryption Key: Select API KEY or dedicated key
- Encryption-only Mode: Activated
pid, lang must be encrypted and included in the encrypted parameter.Scenario 3: API Data Transmission Security Enhancement
Scenario 3: API Data Transmission Security Enhancement
- Secure Data Transmission: Activated
- Encrypt all API requests (Request Body)
- Decrypt all API responses (Response Body)
- Decrypt webhook received data