Webhooks overview and setup.

A webhook is a message the platform sends to an address you choose the moment something happens: a purchase, a stamp, a voucher redemption, a tier change, and more. You do not have to keep checking Reward Loyalty for new activity. Point a webhook at Zapier, Make, your own software, or a screen at the counter, and it hears about the event right away.

APIs write to Reward Loyalty; webhooks only tell the rest of your stack what happened. Nothing outside the platform can create or change a loyalty fact through a webhook.

What you can build

A webhook is one-way: it reports a fact after the platform has already recorded it. Common uses:

• A no-code automation. Zapier or Make catches the event and updates a spreadsheet, posts to Slack, or sends its own email, no code required. See Connect Zapier or Make below.
• Your own tools. Middleware you write and run yourself can react to any event: sync a CRM, trigger a receipt printer, or keep a data warehouse current.
• A screen at the counter. A confirmation display or a till can light up the moment a sale earns points or a voucher is redeemed, pairing this with the purchase API. See Connect any POS.

Turning it on

Webhooks is included through the plan a partner is on. Gold and Platinum include it by default; Bronze and Silver do not. The operator decides which plans include Webhooks, and can grant or revoke it for one partner on top of the plan:

1. The operator opens Admin → SaaS overview → Plans.
2. The operator opens the plans that should include Webhooks.
3. The operator enables Webhooks and saves.
4. The operator can grant Webhooks to one partner on a plan without it, or revoke it from a partner on a plan with it, from Administration → Partners → Permissions.
5. Once entitled, the partner opens Integrations → Webhooks in their own dashboard and adds an endpoint.

If you run a business on Reward Loyalty: your operator turns Webhooks on for your plan. If you have it, you will find it under Integrations → Webhooks. If the entry is missing, your plan does not include it and no per-partner grant does either; ask your operator.

If every active plan has Webhooks off, it disappears from the plan cards on signup and from the My Plan comparison.

Editing a plan sets the Webhooks default for partners created on it or assigned to it, and controls the plan cards; it does not retroactively change partners already on the plan. Each partner keeps their own Webhooks setting until an operator changes it. To change one partner right away, use step 4 above (Administration → Partners → Permissions, which takes effect immediately); assigning or reassigning a partner's plan also re-derives the setting from the plan.

Changing a plan definition never erases a partner's existing setup. An endpoint, its secret, its event choices, and its delivery history all stay in place; losing the entitlement only stops new deliveries and hides the menu, and restoring it brings the setup back.

Adding an endpoint

From Integrations → Webhooks:

1. Click Add endpoint.
2. Name it something recognizable later, such as "Zapier" or "Order display."
3. Paste the URL that should receive events. It must be a public HTTPS address; plain HTTP, localhost, and private network addresses are all rejected, both when you save and again every time an event is sent, since a URL that resolves publicly today could resolve privately tomorrow.
4. A query string or a fragment on the URL (anything from ? or # onward) is dropped before it is saved. If an endpoint needs a parameter, put it in the path, or read it from the delivered payload instead.
5. Choose the events this endpoint should receive. The picker groups them into categories, each with a Select group and Clear group action, and every event shows its machine key plus a badge: Broad, Detailed, Lifecycle, or Privacy. Which groups appear depends on the card types your business uses. At least one event is required. See Events and member synchronization for the full catalog and what the badges mean.
6. Click Save.

The name, address, and event choices are checked as you fill them in. If the address is rejected, the reason appears right under the field so you can fix it without losing the rest of the form.

After you save, the page reloads and shows the signing secret once, in full, in a dialog with a Copy button. The signing secret is a shared password that lets your receiving system prove each delivery is genuine and came from Reward Loyalty; Security and signature verification explains how it works. Copy it now. Once you close the dialog, only the last four characters are shown anywhere in the dashboard; there is no way to see the full value again short of rotating it for a new one.

Each partner can register up to five endpoints. Remove one to make room for another.

An upgrade never changes what an endpoint receives. When a platform update adds event types to the catalog, they stay unselected on your existing endpoints until you edit the endpoint and choose them.

Pausing and re-enabling an endpoint

Every endpoint has an Active switch. Turn it off to stop deliveries without deleting the endpoint or its history, and turn it back on the same way when you are ready again. Reward Loyalty also pauses a failing endpoint by itself after enough failed deliveries in a row and emails the partner who owns it; see Deliveries, retries, and troubleshooting for how that works and how to recover from it.

Rotating the secret

Rotate secret immediately swaps in a different value; the old one stops verifying straight away, so update it wherever the endpoint checks signatures first, or plan for a short gap in deliveries. The new secret is shown once, the same way as when the endpoint was created: copy it from the dialog before you close it.

Connect Zapier or Make

1. In Zapier, create a Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event.
2. Zapier shows a custom webhook URL. Copy it.
3. In Reward Loyalty, add an endpoint under Integrations → Webhooks, paste that URL, then pick the events the Zap should react to.
4. Save the endpoint, then click Send sample with one of the events you picked (or Send ping for a bare connection test). Back in Zapier, use Test trigger to pull in that delivery.
5. Map the fields onto the rest of the Zap, for example event, data.member.id, or data.points_awarded.

Make works the same way: choose Webhooks (or a custom webhook module) as the trigger, and paste the same endpoint URL.

Related topics

• Events and member synchronization: The full 32-event catalog, field tables, and how to keep your own member records in sync
• Security and signature verification: What the signing secret protects, and how to check it in your own code
• Deliveries, retries, and troubleshooting: Test sends, the retry schedule, auto-pause, duplicates, and a troubleshooting table
• Integrations overview: Every available integration in one place
• Connect any POS: Pair these events with the purchase API for a till or a Zap
• Partner permissions & limits: Grant or restrict feature access per partner