API test
api de prueba
2 subscribers
39 endpoints
The in-depth APIMemo review for this API hasn't been published yet —
the data below comes straight from the public marketplace listing.
API test endpoints
| Method | Endpoint | Description |
|---|---|---|
| Secure Streaming | ||
| POST |
resignDataStream /api/crypto/stream/resign |
Receives two parts in multipart/form-data: - 'metadata' (JSON) with 'oldAlias', 'newAlias', and 'oldSignatureBase64' - 'file' (binary) with the data to be re-signed If the old… |
| POST |
reencryptDataStream /api/crypto/stream/reencrypt |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing 'oldAlias' and 'newAlias'. - A binary 'file' part containing the old ciphertext to be… |
| POST |
verifyDataAsymmetricPublicKeyUtilityStream /api/crypto/stream/asymmetric/publickey-verify |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing 'publicKeyBase64', 'signatureBase64' and 'algorithm' (e.g. 'RSA-2048', 'Kyber1024').… |
| POST |
encryptDataSymmetricStream /api/crypto/stream/symmetric/encrypt |
Reads plaintext bytes from the 'file' part in streaming mode and encrypts them using the symmetric key identified by 'alias' in the 'metadata' part. The response is streamed as… |
| POST |
decryptDataSymmetricStream /api/crypto/stream/symmetric/decrypt |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing the alias of the symmetric key to use. - A binary 'file' part with the ciphertext to… |
| POST |
encryptDataAsymmetricStream /api/crypto/stream/asymmetric/encrypt |
Receives the encryption metadata in JSON format (alias, etc.) as a part named 'metadata', and the file or data to be encrypted as a part named 'file'. Streams the resulting… |
| POST |
signDataStream /api/crypto/stream/sign |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing the alias of the private key (RSA, ECC, Dilithium, Falcon, etc.). - A binary 'file'… |
| POST |
decryptDataAsymmetricStream /api/crypto/stream/asymmetric/decrypt |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing the alias of the private key to use. - A binary 'file' part with the ciphertext to be… |
| POST |
encryptDataAsymmetricPublicKeyUtilityStream /api/crypto/stream/asymmetric/publickey-encrypt |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing 'publicKeyBase64' and 'algorithm' (e.g. 'RSA-2048', 'Kyber1024'). - A binary 'file'… |
| POST |
verifySignatureStream /api/crypto/stream/verify |
Receives two parts in multipart/form-data: - A JSON object in the 'metadata' part containing the alias (public key) and the signature in Base64. - A binary 'file' part with the… |
| Authentication | ||
| POST |
login /api/authenticate/login |
Authenticates a user using username and password, checking license as well. If valid, returns an Access Token and a Refresh Token. |
| POST |
appAuth /api/authenticate/app |
Authenticates an application using clientId and clientSecret, plus license check. If valid, returns an Access Token and a Refresh Token. |
| POST |
refreshToken /api/authenticate/refresh |
Generates a new Access Token if the provided Refresh Token is valid and unexpired. |
| Key Management | ||
| POST |
generateSymmetricKey /api/key-management/symmetric |
Generates a symmetric key using the given alias, algorithm, and key size (e.g., AES-256), and stores it in the keystore. **Example**: ```json { "alias": "mySymKey", "algorithm":… |
| POST |
importPublicKey /api/key-management/public-keys |
Imports a Base64-encoded public key into the keystore with the given alias and algorithm. - For a KEM key (Kyber), it is stored as a SecretKeyEntry (alias + "_pub"). - For a… |
| POST |
generateAsymmetricKey /api/key-management/asymmetric |
Generates an asymmetric key pair (public/private) with the given alias and algorithm. Examples include: - **Kyber512**, **Kyber768**, **Kyber1024** (KEM) - **Dilithium2**,… |
| DELETE |
removeKey /api/key-management/{alias} |
Removes a key (and potentially its associated public key) from the keystore. If the alias references a Kyber private key, the corresponding alias+"_pub" is also removed. For… |
| POST |
importPrivateKeyPkcs12 /api/key-management/private-keys |
Imports a `.p12` or `.pfx` file containing a private key (and possibly certificates) into the keystore under the specified alias. If the PKCS12 is password-protected, provide… |
| GET |
listKeys /api/key-management/keys |
Lists all keys and certificates stored in the keystore, including their algorithms (AES, Dilithium, Falcon, Kyber, RSA, SPHINCS, ECC, etc.). The response now provides a… |
| GET |
exportPublicKey /api/key-management/public-keys/{alias} |
Exports the public key associated with the given alias in Base64 format. This works for: - KEM keys (Kyber) - Classical or PQ signature algorithms (Dilithium, Falcon, RSA) - ECC… |
| Administration | ||
| GET |
listHumanUsers /api/admin/users |
Retrieves all users whose type is HUMAN. |
| POST |
createHumanUser /api/admin/users |
Creates a new user with type=HUMAN under the specified client. The password is hashed before storing. |
| GET |
listApplications /api/admin/apps |
Retrieves all users whose type is APPLICATION. |
| POST |
assignRolesToApp /api/admin/apps/{clientId}/roles |
Assigns (replaces) roles for the specified APPLICATION user. |
| DELETE |
deleteHumanUser /api/admin/users/{username} |
Deletes a HUMAN user from the system by username. |
| DELETE |
deleteApplication /api/admin/apps/{clientId} |
Deletes an APPLICATION user from the system by username (clientId). |
| GET |
getHumanUser /api/admin/users/{username} |
Retrieves the HUMAN user details by username. |
| POST |
createApplication /api/admin/apps |
Creates a new user with type=APPLICATION under the specified client. The secret is hashed before storing. |
| GET |
getApplication /api/admin/apps/{clientId} |
Retrieves an APPLICATION user by its username (often used as clientId in the path). |
| POST |
assignRolesToHuman /api/admin/users/{username}/roles |
Assigns (replaces) roles for the specified HUMAN user. |
| Secure | ||
| POST |
encryptDataSymmetric /api/crypto/symmetric/encrypt |
Encrypts the given Base64-encoded data using the symmetric key identified by the given alias (e.g., AES-256). The result includes the IV inside the ciphertext, so the format is:… |
| POST |
resignData /api/crypto/resign |
Verifies the old signature (under oldAlias) for the given Base64 data, then signs again with newAlias. This is useful for migrating from classical (RSA) to post-quantum… |
| POST |
decryptDataSymmetric /api/crypto/symmetric/decrypt |
Decrypts previously encrypted Base64-encoded data using the symmetric key identified by the given alias. The input must be in the format: [1 byte IV length] + [IV] + [ciphertext]. |
| POST |
reencryptData /api/crypto/reencrypt |
Decrypts previously encrypted Base64-encoded data using oldAlias, then re-encrypts with newAlias. Allows migrating ciphertext among RSA, ECC, Kyber (e.g., RSA->Kyber, ECC->Kyber,… |
| POST |
signData /api/crypto/sign |
Signs the given Base64-encoded data using the private key associated with the given alias. Supported private-key algorithms for signing: - **Dilithium** (post-quantum) -… |
| POST |
decryptData /api/crypto/asymmetric/decrypt |
Decrypts previously encrypted Base64-encoded data using the private key associated with the provided alias. Supported algorithms: - **Kyber** (KEM + AES/GCM) - **RSA** (classic)… |
| POST |
verifySignature /api/crypto/verify |
Verifies a signature against the provided Base64-encoded data using the public key associated with the alias. Supported algorithms include: - Dilithium, Falcon (post-quantum) -… |
| POST |
encryptData /api/crypto/asymmetric/encrypt |
Encrypts the given Base64-encoded data using the public key associated with the provided alias. Supported algorithms include: - **Kyber** (KEM) - **RSA** (classical) - **ECC**… |
| License Management | ||
| GET |
getLicenseInfo /api/license-management/license-info/{clientId} |
Returns the license details (plan tier, expiry date) and usage status (operation counts, data usage, etc.) for the specified client. |
API test pricing
| Plan | Price | Rate limit | Quotas |
|---|---|---|---|
| BASIC | Free | — |
|
| PRO | Free | — |
|
