Qualify participant
Qualify or disqualify a participant based on their screener responses. When disqualifying (qualifyStatus: false), include a reason code: MISREPRESENTED, CONTEXT, SCREENER, or OTHER.
Disqualification reason codes
When disqualifying a participant (qualifyStatus: false), provide one or more reason codes:
| Code | Description |
|---|---|
MISREPRESENTED | False or misleading information provided by participant |
CONTEXT | Not enough information about participant |
SCREENER | Answers to screener questions not a match |
OTHER | Other reason (provide details in message) |
Body
Response
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,
researcher, respondent, admin time, final