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.
Liveform Encryption Settings Screen
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 |
How to Use After Algorithm SelectionAfter selecting encryption algorithm, parameters requiring encryption in liveform URL’s Query String must be encrypted using the selected algorithm and encryption key, then used in the form
encrypted={encrypted_data}.Encryption-only Mode
Activate encryption-only mode when you want to encrypt and use all Query String parameters.
Encryption-only Mode Settings
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).
Encryption Key Management Screen

Encryption Key Issuance Popup
| 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.Non-encryptable Parameters
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
View detailed encryption/decryption methods and code examples.
Step 3: Add Encrypted Data to URL
Add encrypted data to theencrypted query parameter.
URL EncodingEncrypted data must be URL encoded before use in URLs.
Secure Transmission Settings
Settings to strengthen security for data transmission via API methods.
Secure Transmission Settings Screen
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
Learn webhook data encryption/decryption methods in detail.
Configuration Guide by Scenario
Scenario 1: Selective Encryption Usage
Scenario 1: Selective Encryption Usage
When selecting encryption algorithm and encrypting only some Query Strings.Configuration:In this case,
- 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)
When encrypting and using all Query String parameters.Configuration:In this case, all parameters except
- 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
When strengthening security for data transmission via API.Configuration:
- Secure Data Transmission: Activated
- Encrypt all API requests (Request Body)
- Decrypt all API responses (Response Body)
- Decrypt webhook received data