Glossary · Integration

Webhook signing

An HMAC over the raw delivery body, sent as a header, so your endpoint can prove the POST really came from the platform.

What is webhook signing?

When you supply a secret, the delivery carries a signature header of the form sha256=<hex>, computed as an HMAC-SHA256 of the raw request body with that secret, alongside headers naming the event and the job. Verification means recomputing that HMAC over the raw bytes — not the re-serialized JSON — and comparing in constant time.

Why it matters

An unsigned webhook endpoint accepts a completion notice from anyone who guesses the URL. The raw-bytes detail is the part people get wrong: re-serializing the JSON before hashing changes the bytes and the signature will never match.

Related terms

See it in context

Back to the full glossary

Put your agent to work. Keep the decision.

Give your agent a real browser, authorize the accounts it may use, and keep control of every step. Repeated runs compile into skills that replay without a model.