Webhooks for your store

You can now have Leal send your store's activity to your own systems as it happens. Open Webhooks in your account settings, paste a URL, and choose which events to send: all of them, or any mix of the seven below.

• Customer joined: a new sign-up from a poster, the app, an import or the API.
• Customer updated: a change to name, email, phone, birthday, or marketing and SMS consent.
• Card issued: a customer got a loyalty card. Includes their Apple Wallet and Google Wallet links.
• Stamps earned and Stamps removed: every change to a card's balance, and where it came from.
• Reward unlocked: a customer now has enough stamps for a reward. Sent once per reward.
• Reward redeemed: a reward was used and the stamps were deducted.

What stores are using it for:

• Adding new customers to a CRM or mailing list the moment they sign up.
• Emailing or texting the wallet links to a new customer from your own email or SMS tool.
• Messaging staff in Slack or Teams when a regular unlocks a free coffee, so they can mention it at the counter.
• Keeping stamp balances in step with a booking system or point of sale.
• Logging redemptions in a spreadsheet to see what your rewards cost each month.

Each request is signed, so your server can check it came from Leal. The signature follows the Standard Webhooks format, which has ready-made libraries for most languages.

Click Send test event to check your endpoint straight away. Each endpoint's page shows the response from its last delivery. If your server doesn't answer, Leal retries up to 10 times over about four hours. An endpoint that hasn't accepted a delivery for three days is paused, so you can fix it and switch it back on.

Developers can manage everything through the API too. The guide at getleal.com/developers/webhooks has example payloads and signature code for Node, Python and Ruby.

Webhooks are on paid plans, like API tokens. Zapier users don't need to change anything: your Zaps keep working as they do today.