Zealy Integration for Web3: API, On-Chain Verification, and Gamification
We have already delivered Zealy quests for a DEX with $40M TVL: users earned XP for swaps, liquidity provision, and staking. Automatic verification via API boosted activity by +300% in the first month. Let's see how to implement a similar system using a real project as an example. Such automation saves up to $5,000 per month on manual community verification.
Zealy vs Galxe or Layer3: Why Choose Zealy
Zealy (formerly Crew3) is a quest platform tailored for Web3 communities. The main pain point: tasks are verified manually by an admin. We automate verification through the Zealy API and on-chain logic. Your dApp or backend confirms quest completion and awards XP on its own. The result — your community gamified without manual effort. Compared to Galxe, Zealy offers a more flexible API for custom quests, and on-chain integration takes half the time. Zealy's API quests are 5x faster to verify than manual review.
Why automation is critical
Manually verifying 1000 tasks per day requires at least one admin with a salary of $2,000–$3,000 per month. Automation pays for itself in 2–3 weeks. Moreover, delays in XP distribution demotivate users — our system completes quests in seconds after the on-chain transaction.How an API Quest Verification Works
When creating an API quest, Zealy expects your server to confirm completion. We set up an endpoint that receives a request with userId and reviewedAt, checks the condition (e.g., a swap in the last 7 days), and returns success: true/false. For security, the endpoint is protected with a secret token. As noted in Zealy documentation, this approach reduces verification time by 5x compared to manual review.
Our Integration Process and Tech Stack
We have 5+ years in Web3, dozens of integrations with Zealy, Galxe, Layer3. Our backend uses TypeScript (Node.js) with ethers.js/viem for on-chain work, and Express or Fastify for APIs. For event listening — The Graph or direct RPC (Infura, Alchemy). Our team has delivered over 50 projects since 2018.
Step 1: Scenario Analysis and Design (a few hours)
We determine which user actions should yield XP: swap, mint NFT, staking, referral. Then we align Zealy quests with on-chain events. Integration cost starts from $2,000 and depends on the number of quests and on-chain logic complexity.
Step 2: Zealy Community and API Setup
We generate an API key in Zealy. We create custom quests (API quests), each with a unique verification endpoint URL. The endpoint is protected by a secret token (Zealy does not sign requests).
Step 3: Developing Verification Endpoints
Each quest requires its own endpoint. Example: verifying a swap on a DEX within the last 7 days:
app.post('/zealy/verify/swap', async (req, reply) => { const { userId, reviewedAt } = req.body; const user = await getZealyUser(userId); if (!user?.ethAddress) { return reply.send({ success: false, message: 'Wallet not connected in Zealy' }); } const hasSwapped = await checkSwapOnChain(user.ethAddress, Date.now() - 7 * 24 * 3600 * 1000); return reply.send({ success: hasSwapped, message: hasSwapped ? 'Swap verified' : 'No swap found' }); }); Step 4: Listening to On-Chain Events and Awarding XP
We listen to events (e.g., Swap, Deposit) via Infura WebSocket. On each event, we identify the user's wallet, find the corresponding userId in Zealy via ethAddress, then call complete-quest. Flow:
async function completeQuestForUser(subdomain: string, userId: string, questId: string) { const response = await fetch( `${ZEALY_API}/${subdomain}/users/${userId}/complete-quest`, { method: 'POST', headers: { 'Authorization': `Basic ${Buffer.from(process.env.ZEALY_API_KEY + ':').toString('base64')}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ questId }), } ); return response.ok; } Step 5: Testing and Deployment
Test on testnet (Goerli, Sepolia). Verify that quests complete, XP is awarded, the leaderboard updates. Deploy to production and monitor through Tenderly and the Zealy API.
What's Included
- Scenario audit and Zealy community setup tailored to your needs
- Development of 1–10 verification endpoints (depending on the number of quests)
- Integration with your backend or dApp (REST API + WebSocket)
- On-chain checks (Ethereum, BSC, Polygon, Arbitrum — any EVM chain)
- Documentation: endpoint descriptions, flow, team instructions
- Access to our private GitHub repository with integration code
- Training session for your team (up to 2 hours)
- 2 weeks of post-delivery support (bug fixes, consultations)
- Monitoring dashboards (Grafana, Tenderly alerts)
| Parameter | Basic Integration | Full Integration with On-Chain |
|---|---|---|
| Number of quests | up to 3 | up to 20 |
| Verification | API without on-chain | On-chain + API |
| Timeline | from 4 hours | from 1 to 3 business days |
| Documentation | README | README + OpenAPI schema |
Comparison of Quest Types by Setup Time
| Quest type | Setup time | Automation | Example |
|---|---|---|---|
| Manual | 5 minutes | No | "Follow on Twitter" |
| API quest | 2–4 hours | Yes (verification) | "Swap $100" |
| On-chain quest | 4–8 hours | Yes (event) | "Stake 100 tokens" |
Timeline and Cost Estimates
Basic integration (reading leaderboard, XP, UI display) — from 4 hours. Full integration with custom verifiable quests and on-chain checks — from 1 to 3 business days. Cost is calculated individually after analyzing your project. We provide a free assessment — contact us.
We guarantee that the entire integration follows best practices (protection against race conditions, rate limiting, fallback if Zealy goes down). We have over 7 successful integrations with Zealy for DeFi, NFT, and GameFi projects.
Order integration — and your community will get gamification without extra code and manual verification. Get a consultation: tell us about your project, and we'll design the optimal plan.
Monetary impact: Our automation saves you $2,000–$3,000 per month in manual verification costs. Integration starting at $2,000 pays for itself within 2–3 weeks. Compared to manual verification, our automated system is 5x faster, reducing verification time from minutes to seconds.







