Crypto for QA Tools

Postman, Bruno, Robot Framework — great for testing, terrible for crypto. Toolkit gives your QA pipeline 40+ REST endpoints for encryption, hashing, and certificates. One HTTP call instead of fighting library limitations.

Core Services

Every crypto operation your test scripts need — without scripting crypto

Data Encoding

Base64, Hex, URL, and CBOR encode/decode. URL query parameter extraction.

6 endpoints

Hashing

MD5, SHA-1, SHA-256, SHA-512. Hash any payload in a single call.

4 endpoints

Symmetric Encryption

AES (ECB, CBC, CFB) with 128/192/256-bit keys. 3DES (ECB, CBC). Encrypt and decrypt.

8 endpoints

Asymmetric Crypto

RSA and ECC key generation, sign/verify, encrypt/decrypt. ECDSA, ECDH, and CSR generation.

12 endpoints

JOSE

JWK generation, JWE encrypt/decrypt, JWS sign/verify. Full JSON Object Signing & Encryption.

5 endpoints

Certificates & Keys

X.509 info extraction, PEM/DER conversion, self-signed certs, CA signing. PBKDF2 key derivation.

7 endpoints

Just HTTP Calls

If your QA tool can send a request, it can do crypto. No plugins, no custom scripts.

Postman — Auth Token
// Pre-request: generate JWT POST {{toolkit}}/api/jws/sign { "payload": {"sub": "test-user"}, "algorithm": "RS256", "key": "{{privateKey}}" } // Use response as Bearer token
Bruno — Encrypted Payload
// Encrypt test data before sending POST {{toolkit}}/api/aes/encrypt { "data": "test card 4242...", "key": "{{aesKey}}", "mode": "CBC" } // Pass ciphertext to your API
Robot Framework — mTLS Setup
*** Test Cases *** Generate Client Certificate ${resp}= POST ... ${TOOLKIT}/api/x509/self-signed ... json={"cn": "test-client"} Set Suite Variable ... ${CLIENT_CERT} ${resp.json()} # Use cert for mTLS tests
Any Tool — Hash Verification
# Verify response integrity curl -X POST /api/hash/sha256 \ -d '{"data": "response body"}' # Compare with expected hash { "hash": "a1b2c3d4e5...", "algorithm": "SHA-256" }

Why Toolkit

QA tools weren't built for crypto. Toolkit fills the gap.

No Scripting Workarounds

Stop writing pre-request scripts in Postman or custom Python helpers in Robot Framework. One REST call does it.

Standards-Compliant

JOSE, X.509, PBKDF2, PKCS padding, OAEP. Correct implementations your tests can trust.

📦

Works With Every QA Tool

Postman, Bruno, Robot Framework, Cucumber, k6, Artillery — anything that sends HTTP requests.

🔧

Production-Ready

Dockerized, structured logging, OpenAPI 3.0 docs, and Postman collections included.

Use Cases

Real QA scenarios where Toolkit saves hours of workaround scripting

API Test Authentication

Generate JWTs, sign requests, or hash credentials directly from your Postman/Bruno collections. No pre-request script gymnastics.

Encrypted Payload Testing

Your API expects AES-encrypted bodies? Encrypt test data via Toolkit, send it, decrypt the response. All within your test flow.

Certificate Validation Tests

Generate self-signed certs, create CSRs, test mTLS flows. Full PKI testing without openssl commands in your pipeline.

Robot Framework Keywords

Call Toolkit endpoints as HTTP keywords in Robot Framework. Crypto becomes a one-liner in your test cases.

Stop Fighting Your QA Tools

Let them do what they're good at. Let Toolkit handle the crypto.