You will receive the Base URL, API key, and testing instructions when your Quest application is approved.
- A Quest is a single earnable action with its own points budget, active window, and rules. Points are always allocated to a user for completing a quest using
POST /quests/{questId}. - A Campaign is a collection or promotion that groups related quests for discovery and presentation (e.g., via
GET /campaigns/{id}orGET /quests). Campaigns don’t hold balances and don’t allocate points—allocations always happen at the quest level.
Authentication
Some endpoints require an API key passed via thex-api-key header. The API key must:
- Start with the prefix
sk_ - Be associated with the quest owner account
Endpoints
Get Quest Details
Parameters
Headers
Response
Status Codes
Get Public Quests
Parameters
Headers
Response
Status Codes
Get Campaign Details
Parameters
Headers
Response
Status Codes
Allocate Quest Points
Parameters
Headers
Request Body
Response
Status Codes
Error Handling
Common Error Scenarios
- Quests Disabled: When the quest feature flag is disabled
- Quest Not Active: When current time is outside quest’s start/end period
- Insufficient Points: When requested points exceed quest’s remaining points
- Account Not Found: When the target address doesn’t have an associated account
- Action Type Inactive: When the quest’s action type is deactivated
Integration Notes
- Address Format: Addresses are automatically converted to checksum format
- Quest Ownership: Only quest owners can retrieve detailed information or allocate points
- Real-time Validation: All requests validate quest status, remaining points, and account existence
- Earning Periods: Points are allocated within the current active earning period
Security Considerations
- Store API keys securely and never expose them in client-side code
- Use HTTPS for all API communications
- Validate addresses on your end before sending requests
- Monitor API usage for unusual patterns