Reward almost any action your users take, anywhere, as long as it can be checked by an API. If something a user does can be confirmed with a web request, Loyalty Stacker can turn it into a quest. Played five matches? Crossed a spending threshold? Hit a daily streak? Renewed a subscription? Finished onboarding in your app? Point us at the place that knows the answer, and we reward it automatically.
What it is
API Integration quests let Loyalty Stacker reward users for actions that happen outside the quest platform, inside a game, an e-commerce backend, a learning platform, a CRM, a referral system, or any service your team runs.
Here’s the simple idea: most software already keeps score. Your game knows how many matches a player has won. Your store knows how much a customer has spent. Your app knows whether someone finished onboarding. All of that lives behind an API, a web address that answers questions about a user.
When a user clicks “Verify,” we ask your system a question about that specific user, read the answer, and check it against a rule you set. If it passes, the reward lands instantly. It’s the most flexible quest type Loyalty Stacker offers, a blank canvas for “reward people for doing this.”
What you can do
Four moving parts turn any endpoint into a reward: who we identify, how we ask, what counts as a pass, and what the user earns, plus a test panel to prove it before launch.
On verify, we send your API a detail that identifies the user: wallet, email, X handle, or a value they type. Send one or several at once.
Call your API as a simple lookup (GET) or a structured request (POST). Protected endpoint? We attach a secret key on every call, stored securely.
Point to the exact value in the response and the rule it must satisfy: equals, exists, greater-than, contains, and more.
Grant points, a badge, a points multiplier (optionally timed), or a soulbound token, and stack several on one quest.
A built-in test panel runs a real check with a sample user detail and shows the exact value your API returned and whether it passed.
Identify the user
When a user verifies, we send your API a detail that identifies them. You choose which one fits your system, and you can send one, or several at once, each under whatever field name your API expects.
- EVM wallet address
- The user’s connected Ethereum-style wallet.
- TON wallet address
- The user’s connected TON wallet.
- Email address
- The email on their account.
- X / Twitter username
- Their connected X handle.
- A typed value
- Anything the user enters themselves: a referral code, a gamertag, an order number, a member ID.
Ask your system its way
We can call your API as a simple lookup (a GET request) or send the user’s details in a structured request (a POST). If your API is protected, we can include a secret access key on every call, stored securely so it’s never exposed.
Define what a “pass” looks like
Your API replies with data, and you tell us exactly which piece to read and what counts as success. The available checks:
| Check | A pass means… | Great for |
|---|---|---|
| equals | the value matches exactly | plan = “premium”, status = “verified” |
| does not equal | the value is anything but X | tier is not “free” |
| exists | the field is present at all | a record was found |
| is true / non-zero | it’s on, true, or above zero | “is eligible”, “has access” |
| greater than | the number is above your threshold | score > 1000 |
| greater than or equal | the number meets your threshold | games played ≥ 5 |
| less than | the number is below your threshold | finished in under N seconds |
| less than or equal | the number is at or under your threshold | placed in top 10 (rank ≤ 10) |
| contains | the text includes your phrase | role list contains “vip” |
Reward however you like
A passing quest can grant any of these, and a single quest can stack several at once:
The reward path is identical to every other quest type, so API quests slot straight into the same leaderboards and multipliers, badges and soulbound credentials as everything else.
Examples & use cases
This is where API quests shine. Below is a recipe book: a marketing goal, the detail we send to identify the user, what your API checks, the operator, and a sample reward. Filter by group or search by field name, and mix and match freely. If your system can answer the question, it can be a quest.
- We send
- Gamertag or wallet
- Checks
- gamesPlayed
- Operator
- ≥ 1
- We send
- Wallet
- Checks
- gamesPlayed
- Operator
- ≥ 10
- We send
- Checks
- gamesWon
- Operator
- ≥ 3
- We send
- Gamertag (typed)
- Checks
- highScore
- Operator
- > 10000
- We send
- Wallet
- Checks
- bestScore
- Operator
- ≥ 5000
- We send
- Checks
- minutesPlayed
- Operator
- ≥ 60
- We send
- Wallet
- Checks
- level
- Operator
- ≥ 20
- We send
- Checks
- currentStreakDays
- Operator
- ≥ 7
- We send
- Gamertag (typed)
- Checks
- sessionCompleted
- Operator
- is true / non-zero
- We send
- Wallet
- Checks
- tournamentRank
- Operator
- ≤ 10
- We send
- Wallet
- Checks
- tournamentRank
- Operator
- = 1
- We send
- Checks
- loggedInToday
- Operator
- is true / non-zero
- We send
- Checks
- hasPurchased
- Operator
- is true / non-zero
- We send
- Checks
- totalSpend
- Operator
- ≥ 100
- We send
- Order ID (typed)
- Checks
- orderFound
- Operator
- exists
- We send
- Checks
- subscriptionActive
- Operator
- is true / non-zero
- We send
- Checks
- planTier
- Operator
- = “premium”
- We send
- Checks
- planTier
- Operator
- ≠ “free”
- We send
- Checks
- accountAgeDays
- Operator
- ≥ 365
- We send
- Wallet
- Checks
- kycStatus
- Operator
- = “approved”
- We send
- Wallet
- Checks
- allowlisted
- Operator
- is true / non-zero
- We send
- Checks
- referralCount
- Operator
- ≥ 5
- We send
- Checks
- roles
- Operator
- contains “vip”
- We send
- Checks
- onboardingComplete
- Operator
- is true / non-zero
- We send
- Checks
- courseStatus
- Operator
- = “completed”
- We send
- Checks
- quizScore
- Operator
- ≥ 80
- We send
- Ticket ID (typed)
- Checks
- resolved
- Operator
- is true / non-zero
- We send
- X / Twitter username
- Checks
- data.linked
- Operator
- is true / non-zero
- We send
- Checks
- apiCallsThisMonth
- Operator
- > 1000
- We send
- Code (typed)
- Checks
- valid
- Operator
- is true / non-zero
What a check looks like
Illustrative only. Your field names and shape are entirely yours. Say you want to reward the “Play 10 matches” milestone. You send the user’s wallet to your stats endpoint, read gamesPlayed from the response, and require it to be ≥ 10.
GET https://api.yourgame.com/players/stats?wallet=0x9f3a…2a1c
Authorization: Bearer •••••••• # your stored secret key{
"gamesPlayed": 14,
"gamesWon": 6,
"level": 22,
"currentStreakDays": 9
}read → gamesPlayed
rule → greater than or equal → 10
value → 14
result → 14 ≥ 10 → PASS → reward granted instantlyIf the value doesn’t pass yet, the user simply sees they’re not there, and can come back and try again later.
Why it matters
Most quest tools stop at “follow us” and “retweet.” API quests reward the actions that actually build a business: playing, buying, subscribing, learning, returning day after day.
No need to rebuild your game or store inside the quest platform. The action happens in your product; the reward happens here. Users barely notice the seam.
Once your team connects an integration, marketing can spin up endless quests on top of it (change the threshold, reward or message) without touching code.
Checks run against your live data the moment a user verifies. No manual review, no honor system, no faked screenshot. The reward only lands when the condition is genuinely met.
API quests grant the same points, badges, multipliers and SBTs as every other quest, so off-platform achievements and on-platform engagement feed the same leaderboards and campaigns.
How it works
Setting up an API quest is a short, three-part conversation between your team and Loyalty Stacker.
- 1Point us at the place that knows the answerThat’s a web address (an API endpoint) your system already has or can expose, for example, the lookup your game uses to fetch a player’s stats. If it needs a secret key to access, you hand that over once and we keep it locked away.
- 2Tell us which user detail to sendPick whatever your system uses to recognize a person: email, wallet, X handle, or a code they type in. When a user hits “Verify,” we pass that detail to your API exactly the way it expects (in the web address, or inside a structured request).
- 3Tell us what a “pass” looks likeYour API answers with a small bundle of data. You point to the specific value that matters (for example, the
gamesPlayednumber) and the rule it must satisfy (“is at least 10”). We read that value, apply the rule, and on a pass the quest completes and the reward is granted on the spot.
Behind the scenes it’s instant and safe: the check runs in real time, waits only a few seconds for your system to respond, and never exposes your secret key. Your team can run a live test at any point to confirm everything reads correctly before going public.
The result: a single, reusable bridge between Loyalty Stacker’s reward system and anything your software can measure, turning almost any user action into a rewardable quest. For blockchain activity specifically, see on-chain & smart-contract quests, or step back to the quest engine overview.