# Changelog

> Notable changes to the AdQuest SDK and public API.

Source: https://dashboard.adquest.io/docs/changelog · Audience: Developers · Section: Resources

## Unreleased (after 1.2.0)

> **Warning: Breaking: activity-proven quests.** The client methods ingestEvent, ingestQuestEvent and attributeReferral, the exports buildQuestEventBody, isEventQuest and mapEventResult, and the QuestEventPayload type are removed. Event, referral and streak quests are proven only by the activities your server reports. The error code STREAK_CALLBACK_REQUIRED is now STREAK_SETTLES_ITSELF.

- A third layout preset, journey, beside default and quests_rewards.
- Multi-step quests: the widget plays every step, and the client adds getQuestExecution, getQuestStep, submitQuestStepEvidence and getQuestReview.
- Quiz quests: graded questions answered one at a time with session.answer(). A first miss returns correct: false and the question is asked again at the end.
- The start splash: enableSplash() or the loader.js script tag covers the embed while it loads, and the embed sends adquest:contentReady.

- [Report activities](https://dashboard.adquest.io/docs/quest-evidence/activities): How your server proves event, referral and streak quests now.
- [Show the start splash](https://dashboard.adquest.io/docs/embed#splash): The script tag and its settings.

## SDK 1.2.0

- A redesigned default layout and skin: larger touch targets, a sticky lottery entry bar, skeleton loading and reduced-motion support.

## SDK 1.1.0

- Quests that hold a place (video, banner, survey, visit) can be reserved on the server. The start response then carries reservation_id, expires_at, server_time and timing; questions are answered one at a time against server deadlines and the widget shows the time left.
- A completed quest is accepted first and settled in the background. The widget shows a pending state and shows the reward only after the server confirms it; headless clients poll GET /platform/quests/{id}/completion.
- A lost response or an expired delivery token never loses an accepted submission: the client asks the server where the attempt stands instead of submitting again.
- Compatible with servers that do not use reservations: nothing changes for them. SDK 1.0.6 keeps working against a server with reservations on, with a 90 second wait before a failed attempt can be restarted.
- Starting, answering and completing a quest need a participant token; the server takes the participant from it.

## SDK 1.0.0

- AdQuestWidget is lottery-first and requires participantToken.
- Quest-only UI is exported as QuestWidget.
- Callbacks: onEntry, onComplete, onClaim, onNavigate, onAuthRequired. The onNavigate payload is { view, canGoBack }.
- Hosted embed with a versioned postMessage bridge.
- Theme tokens for background, surface and CTA edge.

## Migrating from 0.3.x

- Provide participant tokens for balance, entry and claim flows.
- Update callback names if you still listen to older event names.
- Quest tokenReward and completion tokensAwarded now show the participant’s share.
- Browsing quests without a participant token still works. Balance, lottery entries and claims need a signed participant token.

## Next steps

- [FAQ](https://dashboard.adquest.io/docs/faq): Short answers to common questions.
- [SDK reference](https://dashboard.adquest.io/docs/sdk/client): Methods and components.
