Skip to main content
Every webhook meetergo sends is signed with your company’s signing secret, following the Standard Webhooks specification. Verify the signature before you trust a payload. One secret covers all of your company’s webhooks: registered webhook endpoints, form webhook URLs, workflow webhook actions and e-signature completion webhooks.
Signing only adds headers. The request body and Content-Type are unchanged, so existing receivers keep working without changes.

Headers

Signed Content

The signature is an HMAC-SHA256 over this string:
  • The HMAC key is the base64-decoded part of your secret after the whsec_ prefix.
  • The result is base64 encoded and prefixed with v1,.
  • Use the raw request body exactly as received. Parsing and re-serializing the JSON changes the bytes and breaks the signature.

Get Your Signing Secret

Open Integrations & Apps in the dashboard, click the Webhooks tile and reveal the signing secret, or fetch it with an API key:
Revealing or rotating the secret requires a company admin or an API key. Store it like a password.

Verify in Node.js

Any Standard Webhooks library works as well. Pass it the secret, the raw body and the three headers.

Replay Protection

Reject requests whose webhook-timestamp is more than 5 minutes away from your server time, as the sample does. Store recent webhook-id values if you also need to reject a replay inside that window.

Rotating the Secret

Rotate the secret in the dashboard or with the API:
The response contains the new secret and previousSecretExpiresAt. For 24 hours every delivery carries two signatures, one per secret, so a receiver on either secret accepts it. Deploy the new secret within that time. After 24 hours only the new secret signs.

Troubleshooting