The Stedion Loyalty API sits in front of the loyalty platform and gives your team user-scoped endpoints for challenges, rewards, coupons, profile, and tiers. Authenticate with your own JWTs, skip request signing entirely, and build your UI, faster. It is the same API the Loyalty SDK is built on.
Illustrative responses. The member is identified by your JWT: no member IDs in URLs, no request signing.
Every endpoint answers for the member making the request: what they can see, earn, and redeem. Eligibility, segmentation, and aggregation happen behind the API, so your front end reads like the product you are building, not like platform plumbing.
Balance, tier, progress to the next level, and enrollment in one call.
GET /v1/members/me
Available, in-progress, and completed challenges, already filtered for the member.
GET /v1/members/me/challenges
The store the member can afford and qualify for, plus their wallet of coupons.
GET /v1/members/me/rewards
Complete challenges, redeem rewards, and record activity with simple POSTs.
POST /v1/members/me/actions
Every earn and burn, paginated and filterable, ready for a history screen.
GET /v1/members/me/activities
The API trusts tokens your backend issues. You keep full control of authentication, and no secrets ever live in the client.
One aggregated call returns balance, tier, challenges, and rewards from an edge cache close to your members. Short TTLs keep campaigns dynamic, webhooks push changes back into the cache instead of polling, and the loyalty platform itself sees a fraction of the traffic.
Balance, tier, challenges, and rewards in one response, not four round trips.
Answers come from the edge close to the member, with short TTLs that keep campaigns dynamic.
Changes push back into the cache the moment they happen; campaigns go live within seconds.
The loyalty platform sees a fraction of the traffic, which keeps rate limits and costs predictable.
The Loyalty SDK is built on this API, so the two coexist cleanly. Many teams drop in widgets for standard moments like a points balance or a rewards store, and use the API directly where the experience is uniquely theirs. Start either way and mix levels per feature.
The loyalty moment is deeply woven into your own UI, you have strong design opinions, or you are integrating loyalty into surfaces the SDK does not cover yet.
You want the fastest path to live: standard loyalty moments, your brand theme, and central updates from Stedion without another release.
Tell us about your stack. We will walk through the endpoints against your program, live.
Talk to Stedion Explore the Loyalty SDK →