Update a study
Authentication
Path Parameters
Request
Use ‘question’ if you will add a question in your survey or experiment asking the participant ID
Recommended Use ‘url_parameters’ if your survey or experiment can retrieve and store those parameters for your analysis.
Use ‘not_required’ if you don’t need to record them.
Specify at least one completion code for your study. A participant will enter one of these codes when they complete your study.
Each code must be unique within a study.
You can specify as many actions as you like per code. However, some actions can’t be used together (e.g. AutomaticallyApprove and ManuallyReview).
How many participants are you looking to recruit.
Note: This field is optional when data_collection_method is set to DC_TOOL or AI_TASK_BUILDER (AI Task Builder), as the total available places are automatically calculated from the batch configuration.
The ID of a filter set, from which filters for the study will be taken.
Note, this cannot be used in combination with additional filters via the filters field.
Advanced: This helps with faster data collection. Your survey system will need to handle providing a unique experience each time the participant takes the study.
Configuration related to study submissions. The purpose of this field is to capture any configuration options that impact the submissions made by participants in a study.
This field allows you to tag studies with information about the type/topic of the study and the kind of work involved in completing it.
We plan to make this information available to participants for easier self-selection. At present these options are mutually exclusive and only a single option can be selected, however in the future available categories will expand.
The ID of the data collection batch or project from the Task Builder API.
Required when data_collection_method is set to DC_TOOL or AI_TASK_BUILDER.
Array of access_details, which integrates with taskflow.
While this field is nullable, you must provide one of access_details or external_study_url.
The sum of all access_details must add to the total_available_places field, however the values can be different for an individual access_detail.
Response
Array of access_details, which integrates with taskflow.
While this field is nullable, you must provide one of access_details or external_study_url.
The sum of all access_details must add to the total_available_places field, however the values can be different for an individual access_detail.
Specify at least one completion code for your study. A participant will enter one of these codes when they complete your study.
Each code must be unique within a study.
You can specify as many actions as you like per code. However, some actions can’t be used together (e.g. AutomaticallyApprove and ManuallyReview).
The ID of the data collection batch or project from the Task Builder API.
Required when data_collection_method is set to DC_TOOL or AI_TASK_BUILDER.
The ID of a filter set, from which filters for the study will be taken.
Note, this cannot be used in combination with additional filters via the filters field.
Study id. It is created by Prolific. Read only.
Use ‘question’ if you will add a question in your survey or experiment asking the participant ID
Recommended Use ‘url_parameters’ if your survey or experiment can retrieve and store those parameters for your analysis.
Use ‘not_required’ if you don’t need to record them.
Status of the study. Read only.
To change the status you can use /api/v1/studies/{id}/transition/
This field allows you to tag studies with information about the type/topic of the study and the kind of work involved in completing it.
We plan to make this information available to participants for easier self-selection. At present these options are mutually exclusive and only a single option can be selected, however in the future available categories will expand.
Advanced: This helps with faster data collection. Your survey system will need to handle providing a unique experience each time the participant takes the study.
Configuration related to study submissions. The purpose of this field is to capture any configuration options that impact the submissions made by participants in a study.
How many participants are you looking to recruit.
Note: This field is optional when data_collection_method is set to DC_TOOL or AI_TASK_BUILDER (AI Task Builder), as the total available places are automatically calculated from the batch configuration.