Skip to content
vendorLoyalty
Mobile

Your app shows the member’s whole account in one call.

Balance, card, tier progress, recent activity and offers come back from a single request, so the loyalty screen in your app loads fast and stays in sync with the till.

Talk to usHow it works

An app that shows yesterday’s balance loses trust.

Customers buy in store, open the app and expect to see the points. If the app reads from a copy, it is wrong for hours. The app should read from the same ledger the till writes to.

  • A summary built for the account screenProfile, tier, progress to the next tier, balance, pending points, the last five transactions and offer counts, in one response.
  • The card on screenShow the EAN-13 number as a barcode the till can scan. Card colours, logo and programme name come from your programme settings.
  • Offers they can useList the offers a member has received and the ones they qualify for.
  • Full history when they want itPaginated transactions with type, points, source and date.
  • Read-only keys for member screensA dedicated read-only permission for member-facing features means an app key cannot award or deduct points.
  • Updates pushed, not polledWebhooks for points, tier and membership changes let your backend send a push notification the moment something happens.

Everything the account screen needs.

Balance, tier and activity.

One call returns what the loyalty tab in your app shows.

The card on screen.

Show the EAN-13 barcode for the till, in your programme’s colours.

How the app connects.

  1. 01AppThe customer opens the loyalty tab in your app.
  2. 02Your backendYour server, holding the API key, asks Vendor Loyalty for the member’s summary.
  3. 03Vendor LoyaltyReturns balance, card, tier, activity and offers from the live ledger.

What your team sees.

  • “View as member” shows the exact summary, offers and ledger the app shows
  • API keys with read-only member permissions for app backends
For developers

API keys are server-side secrets. Your app talks to your backend, which calls Vendor Loyalty. A TypeScript SDK and an OpenAPI 3.1 specification are available for any other stack.

request.httpHTTP
1GET /api/v1/members/9f3c…/summary
2GET /api/v1/members/9f3c…/tier-progress
3GET /api/v1/members/9f3c…/offers/available
4GET /api/v1/members/9f3c…/transactions?page=2

Who it helps.

  • CustomersThe points from this morning’s shop, already in the app.
  • App teamOne endpoint for the main screen, no loyalty logic in the app.

At a glance.

Endpoints
Summary, balance, transactions, tier progress, offers, available offers
Permission
Read-only member scope
Branding
Programme name, logo, card colours
Push
Via webhooks to your backend

Mobile questions.

No. Keys stay on your server; the app calls your backend.

Related.

Mobile appYour loyalty card, offers and receipts, in your own app.Read moreVouchers & cardsDigital and physical, under your brand.Read moreIntegrationsAny POS or shop that speaks HTTPS.Read more

See it with your own programme.

Tell us about your members, your tills and your shop, and we’ll show you where Vendor Loyalty fits.

Talk to usLoyalty overview

Ready to get started?

Launch a store yourself, or talk to us about connecting ecommerce to the systems you already run.

Start buildingTalk to us

  • Vendor Standard

    Everything you need to launch, manage and grow an online store. From €39/month.

    Explore Commerce

  • Vendor Pro

    Larger catalogs, advanced pricing, complex operations and deeper integrations.

    Explore Scale