Hash Generator API - MD5 SHA256 HMAC CRC32

API ID 14237

Hash text with MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 in one call, sign messages with HMAC and identify which algorithm produced a hash.

846 ms avg response

API Documentation

Endpoints

Request
Hash text. Hash any text with MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 in one call, sign messages with HMAC, and identify which algorithm produced a given hash.
Endpoint ID: 35335
GET https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35335/hash+text
INPUT PARAMETERS

Hash text — Endpoint Features

Object Description
text Required Text to hash (or POST it as the body)
algorithms Optional Comma list: md5,sha1,sha256,sha384,sha512,crc32

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
algorithms
API EXAMPLE RESPONSE
JSON
{
    "length": 5,
    "hashes": {
        "md5": "5d41402abc4b2a76b9719d911017c592",
        "sha256": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824"
    }
}
Hash text — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35335/hash+text?text=hello&algorithms=md5,sha256' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
HMAC signature. Hash any text with MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 in one call, sign messages with HMAC, and identify which algorithm produced a given hash.
Endpoint ID: 35336
GET https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35336/hmac+signature
INPUT PARAMETERS

HMAC signature — Endpoint Features

Object Description
text Required Message (optional)
key Required Secret key
algorithm Optional sha1, sha256, sha384 or sha512

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
key
algorithm
API EXAMPLE RESPONSE
JSON
{
    "algorithm": "HMAC-SHA256",
    "hex": "7c1ce32402750db1149385ac20603beeaca8909906d1e81c08f4f5c7db8fbe94",
    "base64": "fBzjJAJ1DbEUk4WsIGA77qyokJkG0egcCPT1x9uPvpQ="
}
HMAC signature — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35336/hmac+signature?text=hello&key=my-secret&algorithm=sha256' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Identify / verify a hash. Hash any text with MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 in one call, sign messages with HMAC, and identify which algorithm produced a given hash.
Endpoint ID: 35337
GET https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35337/identify+verify+a+hash
INPUT PARAMETERS

Identify verify a hash — Endpoint Features

Object Description
hash Required Hash to check
text Required Original text

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

hash
text
API EXAMPLE RESPONSE
JSON
{
    "match": true,
    "algorithm": "md5"
}
Identify verify a hash — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14237/hash+generator+api+-+md5+sha256+hmac+crc32/35337/identify+verify+a+hash?hash=5d41402abc4b2a76b9719d911017c592&text=hello' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 Hash Generator API - MD5 SHA256 HMAC CRC32 simply include your bearer token in the Authorization header.

Headers
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.

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Hash text with MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 in one call, sign messages with HMAC and identify which algorithm produced a hash.

Hash Generator API - MD5 SHA256 HMAC CRC32 FAQs

Each endpoint returns JSON data. The "GET Hash text" endpoint provides a list of hashes for various algorithms. The "GET HMAC signature" endpoint returns the HMAC signature along with the algorithm used. The "GET Identify verify a hash" endpoint returns a boolean match status and the identified algorithm.

Key fields include "hashes" for the hash values in the "GET Hash text" response, "algorithm", "hex", and "base64" for the HMAC signature response, and "match" and "algorithm" for the hash verification response.

The endpoints accept parameters such as the text to be hashed and the algorithm type for HMAC. Users can specify which hashing algorithms to use in the "GET Hash text" and "GET HMAC signature" requests.

The response data is organized in a structured JSON format. For example, the "GET Hash text" response includes a "length" field and a "hashes" object containing individual hash values. Each response is designed for easy parsing and access to specific data points.

Typical use cases include verifying data integrity, securely signing messages, and identifying hash algorithms for data validation. Developers can use this API for tasks like password hashing, data checksums, and ensuring message authenticity.

Users can utilize the returned data by accessing specific fields in the JSON response. For instance, they can retrieve the hash values for storage or comparison, use the HMAC signature for secure communications, or verify the integrity of data by checking the "match" field.

Data accuracy is maintained through the use of established cryptographic algorithms, which are standardized and widely tested. The API relies on these algorithms to ensure consistent and reliable hash outputs across different requests.

Standard data patterns include consistent hash lengths for each algorithm (e.g., MD5 returns 32 characters, SHA-256 returns 64 characters) and structured responses with clear fields. Users can expect predictable outputs based on the input text and selected algorithms.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs