WooCommerce Webhook Testing — Debug WooCommerce Events Instantly

To test WooCommerce webhooks, you need a public HTTPS endpoint that WooCommerce can POST to. WebhookWhisper gives you one instantly — no CLI, no deployment, no ngrok required. Paste the URL into your WooCommerce dashboard, trigger a test event, and inspect the full payload in real time.

Why Test WooCommerce Webhooks with WebhookWhisper?

WooCommerce webhooks fire on orders, products, coupons, and customer events. They use HMAC-SHA256 signing and are configured directly in your WordPress admin.

WebhookWhisper captures every incoming WooCommerce event with full headers, body, and timing data — so you can debug integration issues without deploying to a public server.

WooCommerce Webhook Events

The following events are commonly sent by WooCommerce:

• order.created
• order.updated
• order.deleted
• product.created
• product.updated
• customer.created

How to Test WooCommerce Webhooks Locally

1. Create your endpoint — Sign up free and get a permanent HTTPS URL in seconds.
2. Add the URL to WooCommerce — Paste your WebhookWhisper URL into your WooCommerce webhook settings.
3. Enable forwarding (optional) — Add a forwarding rule to relay events to localhost:3000 or any local port.
4. Trigger a test event — Use WooCommerce's dashboard or the one-click test sender to fire a order.created event.
5. Inspect in real time — See the full payload, headers, and response in your WebhookWhisper dashboard.

WooCommerce Webhook Signature Verification

WooCommerce signs every webhook request using the X-WC-Webhook-Signature header. Always verify this signature in production to prevent spoofed requests.

// Node.js — Verify WooCommerce webhook signature
const crypto = require('crypto');

function verifyWooCommerceSignature(payload, signature, secret) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex');
  return crypto.timingSafeEqual(
    Buffer.from(expected),
    Buffer.from(signature)
  );
}

Common WooCommerce Webhook Errors

• 401 Unauthorized — Signature mismatch. Check that you are using the raw request body (not parsed JSON) for HMAC verification.
• Webhook not received — Verify the URL is publicly accessible. WebhookWhisper endpoints are always public — no tunneling needed.
• Timeout errors — WooCommerce expects a 2xx response within a few seconds. Respond immediately and process the event asynchronously.
• Duplicate events — WooCommerce retries failed webhooks up to 5 times using exponential backoff. Always use the event ID for idempotency checks.

Frequently Asked Questions

How do I test WooCommerce webhooks for free?

Sign up for a free WebhookWhisper account and get a permanent HTTPS endpoint. Add it to your WooCommerce webhook settings and trigger a test event from the WooCommerce dashboard.

Can I test WooCommerce webhooks without deploying?

Yes. WebhookWhisper gives you a public HTTPS URL that requires no deployment. Use the built-in forwarding rules to relay events to your local development server.

How do I receive WooCommerce webhooks on localhost?

Create a forwarding rule in WebhookWhisper pointing to your local port (e.g. http://localhost:3000/webhook). Every incoming event is relayed to your local server with retry logic.

What is the WooCommerce webhook retry policy?

WooCommerce retries failed webhooks up to 5 times using exponential backoff.