canonical: https://jentic.com/apis/loyalzoo.com/loyalzoo

# Loyalzoo API

Loyalzoo is a merchant loyalty and membership platform whose API lets independent merchants and POS partners run digital stamp cards, points programmes, and paid memberships. The 16 endpoints cover merchant authentication, customer creation and updates, point award and reward redemption, membership subscription management, and payment-method capture. Authentication is bearer-based and obtained via the merchant login endpoint.

## For AI agents

Run a Loyalzoo merchant programme - create customers, award and redeem points, manage subscriptions, and capture payment methods - across 16 endpoints behind a bearer token from the merchant login.

## Scope

Does not handle inventory, full payment-gateway processing for ad-hoc charges, or marketing email sends - use for Loyalzoo merchant loyalty, customers, points, subscriptions, and payment-method capture only.

## Capabilities

- Authenticate a merchant and receive a bearer token for subsequent operations
- Create and update customer records on a merchant's place
- Award or deduct loyalty points and trigger reward redemptions
- List a customer's transaction history for support and reconciliation
- Create and modify recurring membership subscriptions priced in the merchant's currency
- Send a payment-card capture email to a customer and store the resulting card on file
- Retrieve place information so the integration can scope operations to the right merchant location

## Use cases

### POS-integrated loyalty at the till

Independent retailers integrate Loyalzoo into their POS so the till can look up a customer, award points on the transaction total, and redeem available rewards in the same session. The merchant-login flow returns a bearer token that the POS reuses for the day, and POST `/v2/merchant/place/customers/points` handles the award. Most POS partners ship the integration in a few days because the surface is small (16 endpoints) and the bearer token is straightforward.

Example prompt: POST `/v2/merchant/login` to obtain a bearer token, then POST `/v2/merchant/place/customers/points` with the customer ID and earned points after each transaction.

### Merchant-run paid memberships

Cafes and fitness studios use Loyalzoo's subscriptions endpoints to run a paid membership tier - daily coffee, monthly classes - billed against a card the customer captured via the email-capture flow. POST `/v2/merchant/place/customers/{customer_id}/subscriptions` creates the subscription and the modify endpoint handles upgrades or pauses without leaving the merchant dashboard.

Example prompt: POST `/v2/merchant/place/customers/{customer_id}/payments/methods/cards/request` to capture the card, then POST `/v2/merchant/place/customers/{customer_id}/subscriptions` to start the membership.

### Customer service rewind and adjust

Support staff use the customers and points endpoints to rewind a mistaken redemption or correct a missed award. List endpoints surface the customer's history, the points-update operation adjusts the balance, and the trail is retained in the transaction history for audit. This avoids manual database edits when something goes wrong at the till.

Example prompt: GET `/v2/merchant/place/customers/history` for the customer, identify the wrong entry, and POST a corrective points adjustment with a reason string.

### Agent-driven merchant assistant via Jentic

An AI agent embedded in a small-business assistant calls Loyalzoo through Jentic to add a customer, award points, or start a membership without the merchant having to learn the API. Jentic isolates the bearer token from the agent and returns the right operation when the merchant says 'sign up Maria for the monthly coffee membership'.

Example prompt: Use Jentic to search 'create a loyalzoo membership subscription', load POST `/v2/merchant/place/customers/{customer_id}/subscriptions`, and execute it with the customer ID and subscription plan ID.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/merchant/login` | Authenticate merchant and obtain bearer token |
| POST | `/v2/merchant/place/customers/create` | Create a new customer |
| POST | `/v2/merchant/place/customers/update` | Update customer details |
| GET | `/v2/merchant/place/customers/history` | Get customer transaction history |
| POST | `/v2/merchant/place/customers/points` | Award or deduct loyalty points |
| POST | `/v2/merchant/place/customers/rewards` | Redeem a loyalty reward |
| POST | `/v2/merchant/place/customers/{customer_id}/subscriptions` | Create a membership subscription |
| POST | `/v2/merchant/place/customers/{customer_id}/payments/methods/cards/request` | Send payment card capture email |

## Key resources

- **Authentication** — Merchant login endpoint that returns a bearer token for subsequent calls
- **Customers** — Create, update, and list customers at a merchant place plus their transaction history
- **Loyalty** — Award and deduct points, redeem rewards
- **Subscriptions** — Create and modify recurring membership subscriptions
- **Payments** — Send payment-card capture requests and store payment methods on file
- **Place** — Retrieve information about the merchant place the session is scoped to

## Why Jentic

- **Setup:** Wiring the Loyalzoo API by hand means running its two-step merchant login to obtain a bearer token, refreshing that token, and shaping customer, points, and subscription request bodies against api-v2.loyalzoo.com yourself. Through Jentic you install once, import Loyalzoo from the API Directory, store the merchant credentials once, and your agent calls it.
- **Permission scoping:** Loyalzoo puts the customer id in the URL path (`/customers/{customer_id}/...`) for subscriptions and payment methods, so a rule can pin your agent to one customer for those operations. You choose the operations it may call, so ones like capturing a payment card are not included unless you add them.
- **Credential handling:** Your Loyalzoo merchant credentials and the issued bearer token are stored once, encrypted, by your own Jentic One instance, refreshed automatically, and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a Loyalzoo customer' or 'award loyalty points', and Jentic returns the matching Loyalzoo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **LoyaltyLion API** — Ecommerce-first loyalty platform with broader points, rewards, reviews, and webhook support
- **Yotpo UGC API** — Reviews and loyalty platform combining UGC and points programmes
- **Stripe API** — Payment processor for one-off charges outside the Loyalzoo subscription model
- **Calendly API** — Booking API to schedule the appointments that drive Loyalzoo membership usage

## FAQ

### What authentication does the Loyalzoo API use?

Loyalzoo uses bearer-token authentication - call POST `/v2/merchant/login` with the merchant's credentials to receive a token, then send it in the Authorization header for subsequent calls. Through Jentic, both the merchant credentials and the issued bearer are stored in the vault and the agent never holds the raw secret.

### Can I award loyalty points through the Loyalzoo API?

Yes. POST `/v2/merchant/place/customers/points` awards or deducts points (the body specifies the direction and amount). Use Jentic search 'award loyalzoo points' to load and execute the operation with customer ID and point total.

### What are the rate limits for the Loyalzoo API?

Loyalzoo does not publish a fixed rate-limit number; merchant traffic is generally low and the API returns HTTP 429 if a burst is throttled. Jentic surfaces 429 unchanged so the agent can retry with backoff.

### How do I create a paid membership subscription through Jentic?

Search Jentic for 'create loyalzoo subscription', load POST `/v2/merchant/place/customers/{customer_id}/subscriptions`, and execute it with the customer ID and subscription plan. Capture the card first via POST `/v2/merchant/place/customers/{customer_id}/payments/methods/cards/request.`

### Does the Loyalzoo API charge customer cards directly?

Loyalzoo captures and stores cards via the payment-method endpoints and bills them against subscriptions. It is not a general-purpose payment gateway - for one-off charges outside a subscription, integrate a dedicated processor.

### How many endpoints does the Loyalzoo API expose?

16 endpoints across authentication, customers, loyalty, subscriptions, payments, and place. The compact surface keeps an agent's tool list short and predictable for small-merchant workflows.

### Can I limit what my agent is allowed to do with the Loyalzoo API?

Yes. Because you run Jentic One yourself, your own rules decide which Loyalzoo operations the agent may call and which merchant credentials it may use, so you can allow point awards and customer lookups while withholding riskier calls like the payment-card capture request. Loyalzoo also puts the customer ID in the URL path for subscriptions and payment methods (`/customers/{customer_id}/...`), letting a rule pin the agent to a single customer for those operations. Any operation you do not grant, such as capturing a card on file, is simply not available to the agent.