Leal Loyalty API

Name: Leal Loyalty API
Brand: Leal Loyalty API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer30 EndpointsREST

For Agents

Stamp and redeem Leal loyalty cards, manage customers, locations, and rewards across a merchant's loyalty programme.

Connect the Leal Loyalty API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Leal Loyalty API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Leal Loyalty API.

Create, list, and update loyalty card templates that customers earn stamps against

Stamp a customer's loyalty card via POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/stamp

Redeem a customer's loyalty card via POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/redeem

Onboard new customers and update their profile data through the customers endpoints

GET STARTED

Start building with Leal Loyalty API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Leal Loyalty API for, with concrete tasks.

★ POS-Triggered Loyalty Stamping

Connect a point-of-sale system to Leal so that completing a purchase automatically stamps the customer's loyalty card. The integration calls POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/stamp at checkout. Replaces manual app-based stamping at the counter and reduces friction for repeat customers.

Call POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{card_id}/stamp at checkout and confirm the response shows the updated stamp count.

Reward Redemption Flow

Allow staff to redeem a completed loyalty card by calling POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/redeem from a tablet at the counter. The integration first reads the customer's cards via GET /accounts/{account_id}/customers/{customer_id}/customer_cards to verify the card is full. Removes the need to fall back to the Leal admin app.

Call GET /accounts/{account_id}/customers/{customer_id}/customer_cards to find a redeemable card, then POST to its redeem endpoint.

Multi-Location Rewards Catalogue Management

Maintain the rewards catalogue and merchant locations programmatically as the merchant scales. The integration calls the /accounts/{account_id}/rewards and /accounts/{account_id}/locations endpoints to add, update, or retire entries. Useful for chains that change rewards seasonally.

Call POST /accounts/{account_id}/rewards with name='Free Coffee' and the required cost, then PATCH the entry once a quarter to refresh seasonal rewards.

AI Agent Loyalty Concierge

An AI agent acts as a loyalty concierge that creates customer profiles, stamps cards based on purchase webhooks, and redeems rewards on demand. The agent uses Jentic's intent search rather than reading Leal's docs directly, and Jentic stores the Bearer token out of context. Time-to-first-stamp drops from hours to minutes.

Search Jentic for 'stamp a Leal loyalty card', load the schema, and stamp the customer card associated with the most recent purchase webhook.

Key Endpoints

30 endpoints — jentic publishes the only available openapi specification for the leal loyalty api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/accounts/{account_id}/customers

Create a customer

POST

/accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/stamp

Stamp a customer's loyalty card

POST

/accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/redeem

Redeem a customer's loyalty card

GET

/accounts/{account_id}/customers/{customer_id}/customer_cards

List a customer's loyalty cards

POST

/accounts/{account_id}/rewards

Create a reward in the catalogue

POST

/accounts/{account_id}/locations

Create a merchant location

POST

/accounts/{account_id}/customers

Create a customer

POST

/accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/stamp

Stamp a customer's loyalty card

POST

/accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/redeem

Redeem a customer's loyalty card

GET

/accounts/{account_id}/customers/{customer_id}/customer_cards

List a customer's loyalty cards

POST

/accounts/{account_id}/rewards

Create a reward in the catalogue

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Leal Bearer API tokens are stored encrypted in the Jentic vault. Jentic injects the Authorization header at execution time so the merchant token never leaves the vault and never enters the agent context.

Intent-based discovery

Agents search Jentic with intents like 'stamp a loyalty card' or 'redeem a loyalty reward' and Jentic returns the matching Leal operation with its full account and customer-scoped path parameters.

Time to first call

Direct Leal integration: 1-2 days to wire up Bearer auth, account/customer scoping, and the stamp-and-redeem flows. Through Jentic: under 1 hour using search, load, execute.

FAQs

Specific to using Leal Loyalty API through Jentic.

Why is there no official OpenAPI spec for the Leal Loyalty API?

Leal does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Leal Loyalty API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Leal Loyalty API use?

Leal uses HTTP Bearer authentication with an API token issued per merchant account. Jentic stores the Bearer token in its encrypted vault and injects the Authorization header on every call so the merchant token never enters the agent context.

Can I stamp a customer's loyalty card with the Leal API?

Yes. Call POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/stamp where the path includes the merchant account, customer, and the specific customer-card the stamp should attach to. The response includes the updated stamp count and completion status.

What are the rate limits for the Leal Loyalty API?

Leal does not document explicit rate limits in the spec. For POS workloads, plan for sustained throughput around 5 requests per second per account and back off when 429 responses appear; the response body usually carries a retry hint.

How do I redeem a loyalty card through Jentic?

Search Jentic for 'redeem a Leal loyalty card', load the schema for POST /accounts/{account_id}/customers/{customer_id}/customer_cards/{id}/redeem, and execute with the account, customer, and card ids. Jentic injects the Bearer token automatically.

Can I manage merchant locations through the Leal API?

Yes. The /accounts/{account_id}/locations endpoints support listing, creating, fetching, updating, and deleting merchant locations so that multi-store loyalty programmes can be managed without the admin UI.

Leal Loyalty API

Connect the Leal Loyalty API to your agent

Capabilities

Start building with Leal Loyalty API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs