Skip to main content

Response formatting

When collecting screener responses there may be one or multiple responses but generally the content of each response has a predictable set of information returned

Basic Screener response

GET: /v1/projects/{projectId}/screener-responses The example below shows a screener-questions POST and subsequent screener-responses GET. The response itself has information relating to the answered questions themselves as well as the participant. Most of the participant information can be found via a second call using the profile ID. Note you will see an additional question in screener-responses with a null order and text: “End Of Survey”; this is an auto generated question to signal to participants when they have reached the end of a screener. When displaying the responses section of the screener-response it is recommended to share:
  • Time the participant took to complete the screener
  • "totalTime":
  • The incentive the participant took the screener at
    • "project.incentive":
  • Time screener was completed
    • "createdAt":
  • Question, response, and qualify status
    • "questionText":
    • "text":
    • "qualify":

Viewing the profile

/v1/profiles/{profileId}

Understanding qualified responses

"qualified": true, implies:
  • NDA is agree to if present
  • 100% percentage on screener questions
  • Matched on location, age, gender, education, and ethnicity

Skipped questions in responses[]

By default, questions that a participant did not answer (because they were skipped over by skip logic, or because the participant chose to skip an optional question) are omitted from the responses[] array. Organizations that opt in to including skipped questions in screener responses (contact Respondent to enable) receive an entry for every screener question, with skipped questions marked explicitly. Each item in responses[] then includes: Example skipped entries:

Last modified on May 18, 2026