# Multi-step evidence

> API type: multi_step. Own-platform only. One reward after every required step is verified.

Source: https://dashboard.adquest.batriders.ir/docs/quest-evidence/multi-step · Audience: Developers · Section: Quest evidence

## Send evidence per step

Start the quest, read the participant's execution and send evidence for each step with its step_key. A sequential quest rejects a step that is not unlocked yet. Completing the quest settles once, after every required step is verified; calling complete earlier returns MULTI_STEP_REQUIRED.

- Server-signed events: send source=server with the step_key. The v2 signature is HMAC-SHA256, using your platform signing secret, over v2.eventId.eventName.questId.participantId.timestamp.stepKey.stepsVersion.executionId. Sign on your backend only.
- URL callbacks: AdQuest calls your HTTPS URL with an X-AdQuest-Signature-V2 header and expects 200 with verified: true.
- Host-verified steps: grant the capability in the host context.
- Manual review steps: submit evidence; staff approve or reject it.

## Verify the flow

- Test a step started out of order, a resubmitted verified step (a no-op) and an optional step left undone.
- A step event id cannot satisfy another step.
- Participants who started before a new version was published keep the old steps.

## Next steps

- [Multi-step quests guide](https://dashboard.adquest.batriders.ir/docs/multi-step-quests): The full walkthrough: who proves each step, condition steps, signing and errors.
- [Quest evidence overview](https://dashboard.adquest.batriders.ir/docs/quest-evidence): The shared request helper and the completion flow.
- [Set up this quest in the dashboard](https://dashboard.adquest.batriders.ir/docs/dashboard/quests/multi-step): For publishers: configure and publish the quest.