Claiming a quest
Overview
The Claim Quest endpoint allows authenticated users to submit their progress or completion for a specific quest deployment. This process may include verifying required accounts, submitting task inputs, and passing a captcha challenge if enabled.
Key benefits:
Ensures only eligible users can claim quest rewards
Supports custom task input validation
Integrates with hCaptcha for anti-bot protection
How It Works
The user completes the required quest tasks and (if needed) solves a captcha.
The frontend collects all necessary data and sends a POST request to the claim endpoint.
The backend verifies authentication, quest existence, required accounts, and (if enabled) captcha validity.
If all checks pass, the claim is processed and a validation message is returned.
API Reference
POST https://your-community-slug.domino.page/api/quests/{id}/claimRequest Parameters
questId
String
Yes
The unique identifier of the quest being claimed.
deploymentId
String
Yes
The unique identifier of the quest deployment instance.
taskInputs
Array
Yes
User-provided answers or data for the quest's tasks.
captchaToken
String
Conditionally1
The hCaptcha token, required if the quest has captcha enabled.
1 captchaToken is required only if the quest's metadata specifies requireCaptcha: true.
Notes:
The user must be authenticated.
The endpoint automatically includes the user's ID and a referral code (if present in cookies).
Response
On success:
On error (examples):
404 Quest not found400 Captcha token is required400 Failed to verify captcha, please try again.
Examples
Real-World Usage
Related Resources
Last updated