For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Go to app
DocumentationAPI Reference
DocumentationAPI Reference
  • Get Started
    • Overview
    • Terminology
    • API Fundamentals
    • Your first data collection
  • Core Concepts
    • Finding the right participants
    • Reviewing submissions and rewards
    • Testing study set up
    • Monitoring study progress
    • Managing high loads
    • Running AI Task Builder Batches via Prolific’s API
  • Cookbooks
    • Longitudinal or multi-part studies
    • Collecting original data with AI Task Builder Collections
  • Tooling
    • Prolific CLI
Go to app
LogoLogo
On this page
  • Users
  • Terminology
Get Started

Terminology

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Welcome to the Prolific API:
Automate human data collection at scale

Next

API Fundamentals

The Prolific API allows you to build powerful and flexible research workflows, in addition to helping you create tailored user journeys that may involve interacting with third-party services. In this article, we’ll go through a detailed overview of the core user types and a typical flow for researchers using our API to run and manage studies.

Users

Participants: Participants use the Prolific platform to perform tasks or surveys for the studies created by researchers. If you’d like to view more information on who the participants on Prolific are, please take a look at our article: Who are the participants on Prolific?

Researchers: Researchers design and create their studies on Prolific to conduct their research or test their AI models. Researchers can use the Prolific UI or interact programmatically with our API to create, manage, and monitor their studies.

Developers & Administrators: These are specific operational roles on Prolific. While they can also be researchers, in most cases, they’ll be part of the team helping the researchers from an operational perspective. They may work with the API to streamline processes such as dynamic study creation, real-time analysis, or quota management.

Terminology

TermDefinition
StudyA data collection unit containing tasks for participants. Can be surveys, annotations, evaluations, or any structured data collection.
ProjectA group for related studies. Sits between workspace and study in the hierarchy. Useful for grouping experiments, waves, or campaigns.
WorkspaceThe top-level organizational unit controlling access and billing. Contains projects and studies. The hierarchy is defined as: Workspace > Project > Study.
ParticipantAn individual who completes studies on Prolific. Verified through multi-step authentication and ongoing quality checks.
SubmissionA participant’s response to a study. It can be in various states including approved, returned, or rejected.
RewardA monetary reward paid to participants for successfully completing a study.
BonusAn additional monetary reward paid to the participant, often used for high-performing submissions.
Participant groupsCustom participant lists for targeting or exclusion. Useful for longitudinal studies and quality management.
Custom groupsSpecialist participants curated by Prolific for expertise in specific domains (e.g., STEM, Healthcare, languages) or AI task types (e.g., fact-checking, image annotation, comparative reasoning, etc.). Studies can be launched specifically to all participants in a custom group.
HooksWebhooks for event notifications, such as changes in study status.
Filters or Pre-screenersCriteria for participant targeting based on a wide range of criteria, including demographics and behaviour.
Custom screening / In-study screeningQuestions to filter participants beyond available pre-screeners. Used when standard filters don’t meet participant targeting requirements.