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 / Field | Meaning or Use |
|---|---|
| Endpoint | HTTPS event receiver. |
| Event Type | Subscribed Wemblo event. |
| Signature | Request verification value. |
| Retry | Repeated delivery after failure. |
| Idempotency | Processes an event once. |
Step-by-step instructions
- Open Wemblo -> Developer Menu -> Webhooks.
- Define the integration purpose and data direction.
- Create the minimum required credential or subscription.
- Implement from a server-side environment.
- Validate requests and responses.
- Handle errors, retries and duplicates.
- Test with fictional data.
- Review logs.
- Rotate or revoke credentials when required.
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| 401 Unauthorized | Missing, invalid, revoked or wrong-workspace key. |
| 403 Forbidden | Scope or resource permission. |
| 422 Validation | Required field or data format. |
| 429 Rate Limit | Backoff, volume and plan/API capacity. |
| Webhook retries | Endpoint 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:

