Skip to main content

​
Statuses

/v1/projects/{projectId}/screener-responses/{screenerResponseId}/ Updating a participant status in a study happens through screener response endpoints.
Screener responses arrive with a qualified status of true or false based on predetermined criteria. If Respondent passes a participant with qualified = false, your researchers can manually qualify them before inviting. Likewise, disqualify (qualifyStatus: false) participants your own screening rules out before inviting them.Qualification is a flag, separate from the response lifecycle status. Disqualifying does not withdraw an invitation that has already been sent — the response stays INVITED and the participant can still take part. To withdraw an invitation, use Cancel invite; after participation, use Reject.
Hide a participant from the project view. This signals that there is nothing wrong with the participant — they are simply not right for this project.
Pass along booking or task data to the participant. For moderated studies, provide a bookingLink. For unmoderated, provide a meetingLink.
Revert an accidental invitation. The participant loses the ability to schedule a meeting or complete a linked study.
Moderated projects only. After a participant books a time on your platform, send the bookedDate and timezone so their dashboard reflects when they should attend. You can also pass an updated bookingLink with a meeting link.
Moderated projects only. If a researcher cannot make a booked meeting and does not intend to reschedule immediately, this removes the booked time from the participant’s dashboard.
Moderated projects only. Cancel an existing booking and immediately re-invite the participant to book a new time.
Mark a participant as “attended” (moderated) or “complete” (unmoderated). This kicks off incentive payout to the participant.For unmoderated studies and surveys, you can track that a participant finished the task — without triggering payment — by redirecting them through the project’s completionUrl at the end of the task. task.status and screenerResponse.status are independent flags: hitting the completion URL only sets task.status = complete, and calling this endpoint only moves screenerResponse.status to ATTENDED. Use the completion URL as a “ready for review” signal and call this endpoint once you’ve cleared the response for payout.That review window is 24 hours: if you have not acted by then, Respondent marks the response ATTENDED automatically and autopay fires. Calling this endpoint early gives up the remainder of the window. See Completion URL.
Indicates the quality of the response did not meet expectations. Stops a pending incentive payment, marks the participant as Rejected Quality, and sends them a notification email.It only stops a payment that is still pending. On an unmoderated study or survey that means within 24 hours of task completion, before the automatic completion marks the participant attended and autopay fires. Rejecting after that records the rejection but does not cancel a payout that has already been created — contact partner support promptly if the payment needs stopping.
Moderated: Available after the scheduled meeting time has passed. Marks the participant as excluded from the study. Unmoderated/Survey: Indicates the participant did not complete the task. Stops a pending incentive payment and sends a notification email.The same pending-payment limit applies as for Rejected: on an unmoderated study or survey, use it within 24 hours of task completion. After autopay has created a payout, marking no-show does not cancel it.
Flag a participant as a favorite. Useful for identifying high-quality participants you may want to work with again.
Report a suspicious or fraudulent participant. The response’s status becomes CANCELLED and its visibility.status becomes DISMISSED — it is removed from the researcher UI and from default listings (visibilityStatus defaults to VISIBLE). Pass visibilityStatus=DISMISSED on List screener responses if you need them back (that filter may include non-report dismissals), and prefer persisting the screenerResponseId on your side before reporting. Reported participants cannot apply to future studies from your organization, and the Respondent team investigates whether they should be removed from the platform.

​
Skipped questions

Organizations that opt in to including skipped questions in screener responses receive an entry in responses[] for every screener question, with skipped, skippedBy, and shown flags marking questions the participant did not answer. See Collecting responses for the field reference and examples.

​
Example status flows

  • Invite → Schedule → Attended / No show / Reject
  • Qualify → Invite → Schedule → Attended / No show / Reject
  • Invite → Schedule → Cancel booking & reinvite → Schedule → Attended / No show / Reject
Last modified on July 30, 2026