Overview
Galxe’s B2B Credential API provides read-only access for:- User eligibility verification
- Credential information retrieval
- Access control validation
- Requirement checking
Important: The B2B API is designed for verification and querying only. Credential management is handled through the Galxe Dashboard.
Understanding Credentials
Credentials are verification proofs that users earn through various activities:Popular Credential Types
EVM_ADDRESS
: Ethereum-compatible wallet verificationSOLANA_ADDRESS
: Solana wallet verificationTWITTER
: Twitter-based verificationDISCORD
: Discord membership verificationGITHUB
: GitHub contribution verificationEMAIL
: Email verification
Common Verification Methods
- Social Media:
TWITTER_FOLLOW
,DISCORD_MEMBER
,GITHUB_CONTRIBUTOR
- Blockchain:
CONTRACT_NFT_HOLDER
,WALLET_BALANCE
,SNAPSHOT_ORG
- Interactive:
QUIZ
,SURVEY
,VISIT_LINK
- Custom:
API
,REST
,GRAPHQL
Basic Credential Queries
Get Credential Information
Check User Eligibility
1
: User is eligible0
: User is not eligible
Quest-Specific Eligibility
Basic Implementation
Get Credential Information
Verify User Eligibility
Verify Multiple Credentials
Access Control System
Simple Access Control
Usage Examples
Basic Verification
Multi-Credential Verification
Quest-Specific Verification
Access Control System
Common Patterns
User Onboarding Flow
Access Gate Implementation
Sync Status Handling
Check Credential Sync Status
Credentials have different sync statuses that affect reliability:SYNCED
: Data is current and reliableSYNCING
: Data is being updated, may be stale
Best Practices
- Caching: Cache eligibility results for 5-10 minutes to reduce API calls
- Sync Status: Check
syncStatus
field before relying on eligibility results - Error Handling: Always handle network errors and invalid credential IDs
- Quest Context: Use
campaignId
parameter for quest-specific verifications - Rate Limiting: Implement delays between batch requests (200-500ms)
Understanding Sync Status
- Always check the
syncStatus
field in responses - Only rely on results when status is
SYNCED
- For critical verifications, consider waiting for sync completion
- Cache results appropriately based on sync status
Next Steps
- Quest Integration - Using credentials in quest requirements
- Credential API Reference - Complete API documentation
- Authentication - Access token setup