Webhook Payload & Data Structure

When a user checks the opt-in box at checkout, the Woo Checkbox Webhook plugin sends a POST request to your specified Webhook URL. This request includes customer data in JSON format, based on the fields you’ve selected in the plugin settings.

Example Payload

Here’s a sample of what the webhook payload might look like:

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john.doe@example.com",
  "country": "US",
  "phone": "+1-555-123-4567",
  "company": "Example Inc.",
  "address_1": "123 Main Street",
  "address_2": "Suite 100",
  "city": "New York",
  "state": "NY",
  "postcode": "10001"
}

Customization Notes

  • Only the fields you’ve enabled in the plugin settings will be included in the payload.
  • The data is sent as a standard JSON object via a POST request.
  • You can connect this to automation tools like Zapier, Make, SureTriggers, or your own custom webhook receiver.

Need to Test It?

Use tools like:

These platforms will display the payload exactly as your endpoint will receive it.

In this article

Disclaimer

This page may contain affiliate links, meaning we earn a small commission if you purchase through our links—at no extra cost to you.

Bricks Builder, Elementor, FluentCRM, Zapier, Make.com, SureTriggers, and any other product names mentioned in our docs are trademarks of their respective companies. We are not affiliated with or endorsed by these brands. All logos and brand names belong to their rightful owners.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only