SHA256 example
curl -X POST https://aisenseapi.com/services/v1/sha256_hash \
-H "Content-Type: application/json" \
-d '{"data":"Hello"}'{
"sha256_hash": "185f8db32271fe25f561a6fc938b2e264306ec304eda518007d1764826381969"
}Each endpoint uses its own response key. There is no generic hash field.
Available algorithms
| Endpoint | Response key | Result for Hello |
|---|---|---|
| /md5_hash | md5_hash | 8b1a9953c4611296a827abf8c47804d7 |
| /sha1_hash | sha1_hash | f7ff9e8b7bb2e09b70935a5d785e0cc5d9d0abf0 |
| /sha256_hash | sha256_hash | 64-character hexadecimal string |
| /sha512_hash | sha512_hash | 128-character hexadecimal string |
| /crc32_checksum | crc32_checksum | 4157704578 |
crc32_checksum is returned as an integer. The four cryptographic hash endpoints return hexadecimal strings.
Input formats
JSON
Send an object with a data field.
{ "data": "Hello" }Plain text
Set Content-Type: text/plain and send the text as the request body.
curl -X POST .../sha256_hash \
-H "Content-Type: text/plain" \
--data-binary "Hello"File upload
Upload a file with multipart/form-data. The endpoint hashes the submitted file content.
Choose the right result
SHA256 or SHA512
Use a modern hash when you need a content fingerprint or integrity comparison.
MD5 or SHA1
Use these only when an existing format or legacy integration requires them.
CRC32
Use a checksum for quick accidental-corruption checks where cryptographic strength is not required.
File comparison
Hash two files and compare the values to check whether their bytes match.
Security notes
MD5 and SHA1 are not suitable for security-sensitive collision resistance. None of these endpoints should be used to store passwords. Password storage requires a slow, salted password-hashing function.
A hash is not encryption. It cannot be decoded back to the original input. Do not send confidential input to a public service when the hash can be calculated inside your own application.
Verify a hash
POST /hash_verify checks data against a hash from any endpoint on this page. The algorithm is recognized from the hash itself: an integer means crc32, hex strings map by length. A mismatch is a result with match: false, and computed is always included so the difference is visible.
curl -X POST https://aisenseapi.com/services/v1/hash_verify
-H "Content-Type: application/json"
-d '{"data": "Hello", "hash": "185f8db32271fe25f561a6fc938b2e264306ec304eda518007d1764826381969"}'
{ "match": true, "algorithm": "sha256", "computed": "185f8db3..." }