Register a Finch webhook endpoint and verify signatures with HMAC-SHA256

domain: hr-payroll · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a webhook endpoint in the Finch Developer Dashboard; webhooks require a Starter, Pro, or Premier plan (not available on legacy Free/Build plans)
  2. Store the one-time webhook secret shown at creation time
  3. On receipt, extract the Finch-Event-Id, Finch-Timestamp, and Finch-Signature headers, and build the signed content string {webhook_id}.{webhook_timestamp}.{body}
  4. Base64-decode the secret, compute an HMAC-SHA256 digest of the signed content, base64-encode it, and compare against each signature listed in Finch-Signature (space-delimited, to support secret rotation)
  5. Reject the webhook if the timestamp is more than five minutes old, and respond 200 immediately, processing the payload asynchronously

Known gotchas

Related routes

Register a ServeManager webhook and verify inbound payload authenticity using the HMAC-SHA256 signature header
servemanager.com · 6 steps · unrated
Configure Sign In App webhooks to receive real-time visitor sign-in and sign-out events with HMAC-SHA256 signature verification.
developers.signinenterprise.com · 5 steps · unrated
Verify Typeform webhook payloads using HMAC-SHA256 signature checking
typeform.com/developers · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans