Update Participant Status
Hide participant
Hide a participant from the default response list. Hidden participants can still be accessed by filtering explicitly.
PATCH
Hide participant
Body
application/json
Response
200 - application/json
Available options:
PENDING, INVITED, SCHEDULED, ATTENDED, NOSHOW, INVALIDRESPONSE, REJECTEDQUALITY, PAID, CANCELLED The visibility status of the screener response. If a screener response is visible, it can be interacted with (invited etc). If a screener response is not visible, it cannot be interacted with. A screener may be hidden for various reasons, and a screener can change from visible to not visible at any time if a participant or screener is found to be untrustworthy. There is a webhook that will notify the client when a screener response changes visibility.
- This property is set to
true(withqualifiedset tofalse) if the participant has qualified based on their responses to the screener, but is in the process of verifying their identity. - Once the participant has completed ID verification,
qualifiedPendingIdVerificationwill be set to false.- If the verification was successful,
qualifiedwill be set totrue. - If the verification failed,
qualifiedwill remain set tofalseunless they were manually qualified through the qualification endpoint (PATCH /projects/{projectId}/screener-responses/{screenerResponseId}/qualify).
- If the verification was successful,
Available options:
researcher, respondent, admin Available options:
time, final Previous
Trigger manual payoutTrigger an immediate incentive payout to a participant. Use this for ad-hoc payments outside the standard attendance-based flow (e.g., bonus payments or partial compensation).
Next
Hide participant