Integration

Zembula + PAR Punchh

PAR Punchh publishes events for sign-ups, rewards, check-ins and coupons, and Zembula can read the state of an online order. Its Webhooks Manager adapters push those events to Braze and mParticle.

It's our business to grow yours

Book a demo

What Zembula can read from PAR Punchh

PAR Punchh serves restaurants, and its developer portal lists what the platform can publish: user events, loyalty check-ins, gift check-ins, redemptions, rewards, redeemables, marketing and transactional notifications, and coupons. Punchh says that a brand can send a welcome email when a person signs up and a notification when a person earns a reward. Zembula can use those events. It can also read one online order by its order ID.

The order read returns the state of the order, the email address, the first name, the locale and the discount cards. People and rewards use an external ID. Orders use the order ID. Your email service provider sends that value as a merge tag in the image URL.

Punchh has adapters that push its events to Braze and mParticle, and pages for Klaviyo and Iterable exist as well. The events framework needs a Punchh representative to switch it on. API keys for the Ops API come from PAR support.

DataDetailLooked up byHow fresh
Order stateThe current state of one online order.order IDopen time
Order contact detailsEmail, first name and locale on an order.order IDopen time
Discount cards on an orderThe discount cards that an order carries.order IDopen time
Sign-up and profile eventsEvents that publish when a person signs up or changes a profile.external IDset at setup
Reward eventsEvents that publish when a person earns a reward.external IDset at setup
Check-ins, redemptions and couponsLoyalty and gift check-ins, redemptions and coupon events.set at setupset at setup

How the data arrives

  • API: Zembula reads the current state of one order by its order ID through the Punchh ordering API.
  • Webhook: The Punchh Webhooks Manager publishes user, check-in, redemption, reward and coupon events.
  • ESP merge tags: Punchh adapters push events to Braze and mParticle, and your email service provider sends the value into the image URL.

What you need

  • An API key or a data export from PAR Punchh. Zembula sets up the connection for you.
  • Ops API keys from PAR support, and a Punchh representative who switches on the events framework.
  • An order ID or external ID from your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
The events framework (webhooks) needs a Punchh representative to switch it on.Events do not flow until your Punchh representative switches them on.

Ideas for email

  • Show the state of an order in an order status email.
  • Show the discount cards on an order in a follow-up email.
  • Send a reward banner when a reward event arrives.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.