Reference for credentials, bridges, batch API, transformation, and the Playground.
Sign up for a free account to start encrypting your data
Create a Credential (encrypted static data) or a Bridge (proxy to an external URL).
Use the record URL (e.g. /r/{uuid}) with GET, or send custom headers for private credentials.
All data stored in SaltingIO is encrypted using industry-standard AES-256-GCM encryption. This provides both confidentiality and integrity protection.
Control who can access your data with flexible privacy settings and optional password protection.
Encrypted static data stored at rest. You provide the plaintext (e.g. API key, config); it is encrypted client-side and stored. Access returns a JSON body with a single data field containing the decrypted payload, or base64-encoded ciphertext depending on access method.
For programmatic access with X-API-Key, the value may be base64-encoded; decode to obtain the plaintext.
A proxy to an external URL. SaltingIO forwards requests to your destination URL and returns the upstream response. The Bridge URL is public; the upstream API key or auth is stored as headers (Authentication & Headers) and sent only server-side.
For Bridges (and credentials with parameters), define named parameters (e.g. ticker, city) and use {{variable}} in the stored URL or data. Callers pass values as query parameters; they are substituted before the request is executed. Parameter names are case-sensitive.
For Bridges (and single-record requests), you can reshape the response using a select query parameter. The value uses GJSON-style paths.
Return one field, e.g. current.temp_c.
Map output keys to paths: {temp:current.temp_c,city:location.name}.
Provide backup URLs that SaltingIO will try if the primary URL fails. Ensures high availability and reliability for your endpoints.
The Playground (dashboard → Playground) lets you call your records without writing code. Test Credentials and Bridges, try different HTTP methods, and inspect responses.
Select a secret, choose method (GET, POST, PUT, PATCH, DELETE), and set URL parameters, custom headers (e.g. X-API-Key), or a JSON body. Use the Transformation tab to build a select string by clicking response fields.
Send one POST /batch with multiple items. Each item has uuid, optional params, and optional select. Response is an array in the same order.
Credential responses are JSON with a data field. With X-API-Key the value may be base64-encoded. Use "Decrypt Base64" in the Playground to decode data in the UI.
SaltingIO's team management system enables secure collaboration on encrypted data. Create teams, invite members, and manage access with granular role-based permissions.
Set up new teams with custom names and invite members using secure team IDs.
Invite members, assign roles, and manage permissions with granular access control.
Collaborate on encrypted secrets with team-specific access and permissions.
Set up a new team with a custom name
Share team ID to invite collaborators
Set appropriate permissions for each member
Work together on encrypted team secrets
GET|POST|PUT|PATCH|DELETE to https://api.salting.io/r/{uuid}. Bridges respect allowed methods; credentials are typically GET. Send custom headers (e.g. X-API-Key, Content-Type).
X-API-Key header or password in body.
Success returns JSON with one field data (string). With X-API-Key the value may be base64; decode to get plaintext.
POST /batch with a requests array. Response order matches request order. Requires auth (e.g. session cookie).
{ "requests": [
{ "uuid": "..." },
{ "uuid": "...", "params": {}, "select": "..." }
] }We cannot read your encrypted data. Only you have the keys to decrypt your information.
Data is encrypted on your device before transmission and stored encrypted on our servers.
We don't track your usage patterns or store any personal information beyond what's necessary.
Join thousands of developers and businesses who trust SaltingIO to secure their sensitive data.