AI Assistant (Leat MCP)
July 20
→
Activation APIs & webhooks
Run the program on any surface you build. Identify customers, award value, and validate redemptions from a kiosk, an app, or a system Leat doesn't natively support. Because the API exposes everything the dashboard can do, a surface you build is never a lesser version of the program.
A kiosk, an app, an order-at-table screen, or an in-house POS identifies a customer by scanning a pass, entering a code, or authenticating a session, and receives their tier, balance, and available rewards. The Registers API is built for this: short calls, designed for a counter or a screen, returning what the surface needs to show and nothing it doesn't. A customer-facing surface can hold a secure session for the customer so they act on their own account without staff involved.
Send an order and process it for loyalty in one call. Award points from a booking system, a WiFi login, or an in-store game. Issue a voucher when a delivery partner confirms an order. Add a stamp from a device that has nothing to do with the till. Any system that knows something happened can turn it into loyalty value, under the same earning rules and Governance as every other channel.
Check a voucher, a reward, a gift card, or a member price before the surface applies it, and get an answer with a reason: valid, or declined because of expiry, stacking, eligibility, or a cap. The same rules that run on the POS run here, so a kiosk never honors something the till would refuse. Validation is a single call, fast enough to sit inside the tap that adds the item.
A tier change to the CRM. A redemption to accounting. A balance update to the app's own cache. A referral completion to the marketing platform. Webhooks fire as events happen, subscribed from the API, the dashboard, or an automation, and carry the payload the receiving system needs. Leat stays the source of truth while the rest of the stack stays in step with it.
The Orders API brings in every order from your POS, webshop, delivery platform, or app, line by line and tied to the customer who placed it. That shows you who orders what: which products your regulars come back for, what first-time customers try, and how baskets differ by location or channel. Orders are a source for segmentation, so you can group customers by what and how they buy, not only by their loyalty activity. The same data shows where to change things: which products to feature, which offers to rethink, which customers to reach. And because each order sits on the customer's record next to the campaigns, vouchers, and rewards that reached them, you can check the revenue your program actually brought in, not just the revenue it happened to be near.
Kiosk and order-at-table loyalty
Recognize and reward customers on self-service surfaces
Custom integration build
Connect a system Leat doesn't support out of the box
Same-visit rewards
Reward a purchase while the customer is still in the store
Data warehouse sync
Stream loyalty and customer events to your analytics stack as they happen
Online and in-store recognition
Recognize the same person whether they buy at the counter or in your webshop
