Verify Webhook Requests & Signatures

Verify supported webhook signatures, timestamps, secrets, and request bodies before processing events.

Overview

Use the exact verification method in the current Wemblo webhook reference. Where signatures are supported, preserve the raw request body, calculate or verify the signature with the webhook secret, compare safely, validate timestamp freshness, and reject invalid requests before processing customer data.

Who should use it

Authorized developers and technical workspace users.

Where to find it in Wemblo

Wemblo -> Developer Menu -> Webhooks

Before you begin

  • Use a server-side integration environment.
  • Create separate test and production credentials.
  • Use HTTPS and least privilege.
  • Never expose a key or webhook secret in client-side code.

Main concepts and fields

Concept / FieldMeaning or Use
EndpointHTTPS event receiver.
Event TypeSubscribed Wemblo event.
SignatureRequest verification value.
RetryRepeated delivery after failure.
IdempotencyProcesses an event once.

Step-by-step instructions

  1. Open Wemblo -> Developer Menu -> Webhooks.
  2. Define the integration purpose and data direction.
  3. Create the minimum required credential or subscription.
  4. Implement from a server-side environment.
  5. Validate requests and responses.
  6. Handle errors, retries and duplicates.
  7. Test with fictional data.
  8. Review logs.
  9. Rotate or revoke credentials when required.

Test and verification

  1. Complete one successful path with fictional data.
  2. Complete one invalid, failure or permission path.
  3. Confirm the result appears in the correct workspace and module.
  4. Confirm the correct person or team can review and continue the work.

Common issues and solutions

IssueWhat to Check
401 UnauthorizedMissing, invalid, revoked or wrong-workspace key.
403 ForbiddenScope or resource permission.
422 ValidationRequired field or data format.
429 Rate LimitBackoff, volume and plan/API capacity.
Webhook retriesEndpoint response, signature, timeout and processing speed.

Security, privacy, consent, cost and provider notes

  • Use only data the business is authorized to process.
  • External provider charges, policies, approvals, limits and availability remain separate.
  • Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
  • Use human review for sensitive, regulated, urgent, financial or final decisions.

Last reviewed: