Hash a payload for a content fingerprint, HMAC-sign it to prove who sent it, and CRC32 it for a cheap integrity check — all in one call.
Developer 5 min read
POST /tools/hash-text
{"text":"{\"order\":1234,\"amount\":49.0}","algorithm":"sha256"}hash-text returns real cryptographic digests (sha256 by default, the full family available) — useful as a content fingerprint for dedup or integrity checks.
A hash alone doesn't prove who sent it. hmac computes an HMAC digest over a key-message pair — the same construction a webhook signature check verifies against.
For a fast, non-cryptographic integrity check (not a security control — just corruption detection), crc32 computes a CRC-32 or Adler-32 checksum. The api-payload-security template runs all three over the same payload in one call: hash, HMAC, and checksum together.