HMAC-sign an API request string
When signing API requests, you concatenate the HTTP method, path, and timestamp into a canonical string, then sign it with your secret key using HMAC-SHA256. The resulting hex digest is sent in the X-Signature header.
What it solves
Generate an HMAC-SHA256 signature for a request payload to authenticate API calls.
Input → Output
HMAC Generator input → HMAC Generator output across 1 step.
Runs in
2–3 minutes · fully local in your browser.
Before you start
- A canonical request string (method + path + timestamp)
- A secret key known to both client and server
The pipeline
-
Generate HMAC (Keyed-Hash Message Authentication Code) with SHA-1/256/512. Free, private, and 100% client-side.
Params: algorithm=SHA-256, key=my-secret-key, outputFormat=hex
Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.
▶Run this workflow
Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.
Pipeline progress
- HMAC Generatorhmac-generator
Sample input
GET /api/data 1700000000
Expected output
79517301cb2bbff5118ba603407d58d99d6fa4c6b7a2e9407b62a7cb26909aca
This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.
Related workflows
You might also need
Workflows sharing tools or topics with this recipe.