Streak evidence

Call the callback URL with a user id#

The SDK can start the quest and call getStreakStatus(id) to render currentDay, dayCount, unlocked, nextUnlockAt and lastCompletedDay. It cannot submit a streak day. After the user finishes that day's action in your product, your backend calls the generated callback URL with that user's stable id. AdQuest records the current unlocked day.

curl -X POST "https://api.adquest.batriders.ir/api/v1/streak-callbacks/YOUR_CALLBACK_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Idempotency-Key: optional-unique-key" \
  -d '{"user_id":"player-123"}'

{
  "user_id": "player-123",
  "external_user_id": "player-123",
  "userId": "player-123",
  "externalUserId": "player-123"
}

Verify calendar behavior#

• Call the URL twice on the same local day and confirm the second response is idempotent.
• Miss a day and confirm reset or freeze matches the quest rule.
• Confirm only the final qualifying day settles the full quest reward.
• Rotate the callback URL if it is exposed and update your server.

Next steps#