Mark as attended
Mark a participant as having attended the study session. This triggers the incentive payment process — ensure the session is complete before calling.
Attendance and the first payment
Whether marking a participant as attended fires the first payment depends on the project’sautomations.autopay setting (see Create a project or read it back with Get a project).
autopay: true(the default when omitted at project creation): calling this endpoint automatically charges the first incentive payment to your team’s default payment card and pays the participant. Do not also call Trigger manual payout withpayoutCount: 1for the same participant — that would issue a second, duplicate payment.autopay: false: this endpoint marks the participant as attended but does not issue any payment. You must send the first payment yourself by calling Trigger manual payout withpayoutCount: 1, or by processing the payment from the Respondent dashboard.
autopay is true. To decouple attendance from payment for a project, set automations.autopay to false at project creation (or via Update a project) and drive all payments through Trigger manual payout.
For projects that pay participants more than once, see How to use multiple payments.Response
PENDING, EXTERNAL_SCREENER_IN_PROGRESS, 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 Read-only. Which quota segments this response occupies and in which consumption tier. Present when the project has a quota.