Hashing checksum
Exacthashing_checksumDeterministic and authoritative — the canonical answer for this input.
Compute a hex digest of a string using a common hash or checksum. Supports md5, sha1, sha224, sha256, sha384, sha512, sha3_224, sha3_256, sha3_384, sha3_512, blake2b, blake2s, adler32, and crc32 (hyphens/underscores in the name are tolerated). Use for cache keys, content-addressed lookups, and integrity checks. Not for password hashing — use a dedicated key-derivation function. Processing multiple inputs? Use `hashing_checksum_batch` to do up to 1000 in one call.
Parameters
textstringrequiredString to hash.
algorithmstringoptionalOne of: md5, sha1, sha224, sha256, sha384, sha512, sha3_224, sha3_256, sha3_384, sha3_512, blake2b, blake2s, adler32, crc32. Hyphens/underscores tolerated.
Call it
curl -X POST https://api.snipget.ai/v1/hashing/checksum \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"text":"hello world","algorithm":"sha256"}'The Batch tab sends up to 1000 inputs in one call via /v1/hashing/checksum/batch.
Example response
{
"is_valid": true,
"algorithm": "sha256",
"digest": "b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9",
"digest_length": 64,
"bytes_hashed": 11
}FAQ
What is this good for?
It turns any piece of text into a short fixed fingerprint. That fingerprint is handy for cache keys, content-addressed lookups, deterministic IDs, or checking that a file or message has not changed since you last saw it.
Will the same text always give the same fingerprint?
Yes. This is an exact, deterministic tool, so the same text and algorithm always produce the identical digest. That is exactly why it works for comparing two values or detecting changes.
Can I use this to store passwords?
No. Plain hashes like MD5 or SHA-256 are not safe for passwords. Use a dedicated password hashing method (like bcrypt) for that. This tool is for integrity and identity, not for protecting secrets.
Which algorithms can I pick?
md5, sha1, the SHA-2 family (sha224, sha256, sha384, sha512), the SHA-3 family, blake2b, blake2s, plus the lightweight checksums adler32 and crc32. Hyphens and underscores in the name are tolerated, and sha256 is the default if you leave it out.
What if I send an unsupported algorithm name?
An unknown algorithm name is a request mistake: the call is rejected with an INVALID_INPUT error listing the supported names, and rejected calls are not billed. Retry with a valid algorithm.