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 participants your own screening rules out before inviting them. The body requires all of qualifyStatus: false, qualifiedOverriden, disqualifyReasons (an array of MISREPRESENTED, CONTEXT, SCREENER, OTHER) and message.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.When the project has a quota, the invite is always admitted: it does not return 409, consumption is recorded, and the bucket may go over target. The response includes quotaAssignment (segments[], tier, revision, assignedAt, tierChangedAt) so you can see which buckets the participant occupies.
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. Researcher-initiated. If the researcher cannot make a booked meeting and is not rescheduling now, call Cancel booking. Less than 4 hours before start, or after start, the response becomes ATTENDED and they are paid. 4 hours or more before, status is CANCELLED and they are not paid. Same 4 hour charge window for remote and in-person.Do not use this when the participant asked to cancel. That pays them inside 4 hours. Use Cancel booking (participant request) instead. See Scheduling.
Moderated. Participant-initiated. Always CANCELLED. Never paid.
Moderated. Researcher-initiated. Cancel the booking and re-invite them to pick a new time. Rejected less than 4 hours before start, remote and in-person.
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.
On moderated Partner API and external bookings, wait more than 15 minutes after start. Status is NOSHOW. They are not paid. Do not use Cancel booking as a no-show. After start that path still pays. On unmoderated studies and surveys, status is INVALIDRESPONSE when 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
  • Invite → Schedule → Participant cancel (never paid)
  • Invite → Schedule → Researcher cancel (4 hours or more: cancelled; less than 4 hours: attended and paid)
Last modified on September 15, 2026