PureSpectrum
PureSpectrum websiteHelp center
PureSpectrum websiteHelp center
  1. Guides
  • Intro
  • API Overview
  • Definitions
  • Survey Lifecycle
  • Create Your First Survey
  • Redirect URLs
  • Changelog
  • HTTP Status Codes
  • General Reference Codes
    • Survey Status Codes
    • Respondent Status Codes
    • Survey Category Codes
    • Age Unit Codes
    • Currency Codes
    • Survey Localization Codes
  • Guides
    • Getting Started
    • Create Survey Examples
    • Multi-Country Surveys
    • Children Age & Gender
    • Append Respondent Demographics to the Survey Entry Link
    • Test Survey Flow
    • Supplier Blends & Groups
    • Respondent Exclusion / Recontact
    • Survey Exclusion Group
    • Quotas on Clicks
    • Field Evenly Over Time (FEOT)
    • Quota Based Pricing (QBP)
    • Quota Level Complete (QLC)
    • Quota Throttling
    • Templates
    • Bypassing Automatic Variable Mapping
    • Research Defender's Predupe
    • Subscriber Emails
    • Real-Time Notifications (SNS)
  • API Reference
  • Schemas
    • Feasibility
      • Feasibility request schema
      • Feasibility response schema
    • Surveys
      • Create survey full request schema
      • Create survey minimum request schema
      • Create survey response schema
      • Update survey status request schema
      • Update survey status response schema
      • Get survey status response
    • Qualifications
      • Qualification Schema
      • Create qualification request schema
    • Quotas
      • Quota Schema
      • Create quota request schema
      • Create quota response schema
    • Attributes
      • Get attributes response
    • Supplier management
      • Supplier
      • List of all suppliers response
      • List of all suppliers per survey response
      • Update the list of suppliers for a Survey request
      • Update the list of suppliers for a Survey response
    • Other
      • Generic error response
  1. Guides

Subscriber Emails

PureSpectrum surveys send notifications to email subscribers for important events.
You may subscribe an email address to these events either through the UI on the Final Details page
image.png
or via the API using the "subscriber_emails": [] parameter.
Example:
Emails must be passed in as strings, must use valid email format ans must be separated by commas.
{
    "survey_localization": "en_US",
    "completes_required": 100,
    "expected_ir": 70,
    "expected_loi": 10,
    "field_time": 5,
    ...
    "subscriber_emails": ["researcher@youremail.com","support@youremail.com"]
}
The subscription list is a property of the survey. Updating the list in one survey will not update subscriber lists in other surveys.
Modified at 2025-07-16 12:03:50
Previous
Research Defender's Predupe
Next
Real-Time Notifications (SNS)