Getting Started
Common Integration Patterns
Reusable code patterns and GraphQL queries for efficient Galxe integration
Authentication & Setup
Basic GraphQL Client
Error Handling with Retry
Quest Patterns
Quest Status Validation
User Eligibility Check
Pagination Patterns
Standard Pagination Query
Fetch All Pages
Leaderboard Patterns
User Position Search
No Direct User Lookup: The B2B API does not provide direct user position lookup. You must search through leaderboard pages to find a specific user.
Credential Patterns
Batch Eligibility Check
Credential Validation
Real-time Monitoring
Simple Polling Monitor
Rate Limiting
Simple Rate Limiter
Data Transformation
Standardize User Objects
Format Points and Rankings
Utility Functions
Time Helpers
Validation Helpers
Best Practices Summary
- Always validate inputs before API calls
- Implement retry logic for network failures
- Use pagination for large datasets
- Cache frequently accessed data (30-60 seconds)
- Handle rate limits with exponential backoff
- Monitor for errors and log appropriately
- Use environment variables for sensitive data
Quick Reference
Essential Queries
- Quest status:
quest(id) { status startTime endTime }
- User eligibility:
quest(id) { credentialGroups(address) { conditions { eligible } } }
- Leaderboard:
space(id) { loyaltyPointsRanks(cursorAfter) { list { rank points address { username } } } }
- User search: Must paginate through leaderboard to find specific users
Common Response Patterns
- Paginated:
{ pageInfo { hasNextPage endCursor } edges { node { ... } } }
- User objects:
{ address { username address } }
or{ username address }
- Error format:
{ errors [{ message extensions { code category } }] }
Next Steps
- Quest Guide - Complete quest implementation
- Leaderboard Guide - Advanced ranking features
- API Reference - Detailed API documentation