About the API:
This API will allow you to convert any text to the desired encrypted type. Supports MD5, SHA1, SHA256, SHA384, and SHA512. Also, you will be able to decrypt them as well.
This API will receive a string and you will be able to encrypt it in the format you want. Later, receive a Hash that you can store.
Besides the number of API calls per month, there are no other limitations.
{"status":200,"success":true,"method":"sha256","encrypted":"eyJpdiI6IkM5Zk1jb1BVNk9jOFdScm5jSjdJMEE9PSIsInZhbHVlIjoiVzk4eUIwL1BZZWtZdkV1bVk4dHo4MDkrMU1iMUdHS0swbXFBYjhkZVlZVT0iLCJtYWMiOiJkNGI3ZmVjMTVmOGM5YmNkZGE0MzA3YzAxMTQxMjkzZGMxN2JjZDdjMmI4OWNkMDIzNzY2NDRhMmRmM2UwNmJiIiwidGFnIjoiIn0="}
curl --location --request GET 'https://pr213-testing.zylalabs.com/api/145/encryption+and+decryption+api/182/encrypt?data=parse this string&method=sha256' --header 'Authorization: Bearer YOUR_API_KEY'
{"status":404,"success":false,"message":"Encrypted data not found"}
curl --location --request GET 'https://pr213-testing.zylalabs.com/api/145/encryption+and+decryption+api/183/decrypt?encrypted=eyJpdiI6IkM5Zk1jb1BVNk9jOFdScm5jSjdJMEE9PSIsInZhbHVlIjoiVzk4eUIwL1BZZWtZdkV1bVk4dHo4MDkrMU1iMUdHS0swbXFBYjhkZVlZVT0iLCJtYWMiOiJkNGI3ZmVjMTVmOGM5YmNkZGE0MzA3YzAxMTQxMjkzZGMxN2JjZDdjMmI4OWNkMDIzNzY2NDRhMmRmM2UwNmJiIiwidGFnIjoiIn0=&method=sha256' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Encryption and Decryption API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Encrypt endpoint returns a JSON object containing the status, success flag, method used for encryption, and the encrypted string. The Decrypt endpoint returns a JSON object with the status, success flag, and a message indicating whether the decryption was successful or if the encrypted data was not found.
Key fields in the Encrypt response include "status" (HTTP status code), "success" (boolean indicating success), "method" (encryption type), and "encrypted" (the resulting hash). In the Decrypt response, key fields are "status," "success," and "message" (providing details on the operation).
The Encrypt endpoint accepts two parameters: "type," which specifies the encryption method (e.g., md5, sha256), and "string," which is the text to be encrypted. Users can customize their requests by selecting different encryption types based on their needs.
The response data is organized in a JSON format. For the Encrypt endpoint, it includes fields for status, success, method, and the encrypted string. The Decrypt endpoint organizes its response similarly, focusing on status, success, and a message for user feedback.
Typical use cases include securely storing passwords, verifying data integrity, and sharing sensitive information within organizations. Users can encrypt data before transmission and later decrypt it for validation or access control purposes.
Users can utilize the returned encrypted string for secure storage or transmission. The success flag helps determine if the operation was successful, while the method field indicates which encryption algorithm was used, aiding in compatibility checks during decryption.
The Decrypt endpoint provides information on whether the decryption was successful and includes a message if the encrypted data is not found. It requires the encryption type and the hash to perform the decryption, ensuring users can retrieve original data if available.
Data accuracy is maintained through the use of established cryptographic algorithms for encryption and decryption. The API relies on well-tested methods, ensuring that the encrypted outputs are consistent and reliable when the correct parameters are provided.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund