Crittora Secure overview
Crittora Secure is managed cryptographic infrastructure for signing, encrypting, decrypting, and verifying sensitive payloads across applications and partner workflows.
Capabilities
Sign and encrypt
Purpose: Create a signed encrypted payload in one managed API call.
Endpoint: https://managed.crittoraapis.com/sign-encrypt
Start quickstartDecrypt and verify
Purpose: Allow authorized recipients to decrypt payloads and verify the signer before trusting the data.
Endpoint: https://managed.crittoraapis.com/decrypt-verify
View API exampleApp client access
Purpose: Issue separate credentials for applications, teams, or workflows with scoped E/D/S/V permissions.
Plan: Pro portal accounts
Open portal docsTransaction visibility
Purpose: Review monthly operation counts and transaction records for a selected date range.
Plan: Pro portal accounts
Open portal docsDeveloper workflow
- Create a Crittora Secure account or app client.
- Copy and store the one-time credentials.
- Call sign-encrypt with the sensitive data and optional permissions.
- Store or transmit the returned encrypted_data value.
- Call decrypt-verify as an authorized recipient before trusting the data.
Credential headers
| Header | Description |
|---|---|
| username | Account or app client username |
| password | Account or app client password |
| api_key | Crittora partner API key |
| access_key | Crittora partner access key |
| secret_key | Crittora partner secret key |
Access model notes
Permissions are application-layer controls tied to partner IDs or app clients, not raw key distribution. Use separate app clients whenever separate systems should not share the same access.
Do not assume access revocation for previously granted payload access unless a newer product update explicitly confirms that behavior.
Secure summary
Credentials are displayed once after trial or app client creation. Store them securely before leaving the success page.