PureSpectrum
PureSpectrum websiteHelp center
PureSpectrum websiteHelp center
    • Intro
    • API Overview
    • Definitions
    • Survey Lifecycle
    • Create Your First Survey
    • Redirect URLs
    • Changelog
    • HTTP Status Codes
    • API Rate Limits
    • Status Page
    • Quick Integration Steps
    • General Reference Codes
      • Survey Status Codes
      • Respondent Status Codes
      • Survey Category Codes
      • Age Unit Codes
      • Currency Codes
      • Survey Localization Codes
    • Guides
      • Getting Started
      • Quick Start
      • 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)
      • Integrations Process
    • 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

    Quick Integration Steps

    🚀 Good Integration Guide#

    Integration depth with the PureSpectrum Buy API varies by buyer - this guide covers the core functionality we recommend most integrations include to get the most value from the platform.

    Attributes#

    Fetch targeting questions by locale, with qualification codes, condition codes, and answer ranges where applicable. These codes are required later for survey targeting and quotas.
    Call this endpoint periodically to stay in sync as questions and answers are added.
    Attributes endpoint docs →

    Feasibility#

    Get maximum feasibility and suggested pricing based on field time, completes, LOI, IR, and targeting criteria - before launching. Adjust and retry to further tweak.
    Use this to inform pricing. If end users create their own surveys in your tool, add your markup on top of the returned price.
    Feasibility endpoint docs →

    Create Surveys#

    Create surveys with your targeting criteria, using the qualification and condition codes returned by the Attributes endpoint.
    Create survey docs →

    Update Surveys#

    Use the update endpoints to adjust surveys pre-launch or in-field, so you can react quickly to fielding or performance issues.
    Prefer PATCH over PUT where available - PATCH updates only the fields you send, while PUT requires a full overwrite. Survey status and offer price each have their own dedicated endpoint.
    Update survey (PATCH) →
    Update survey (PUT) →
    Update survey status →
    Update offer price →

    Add Quotas#

    Quotas are usually set at launch. Use the add endpoint to set up quotas on a survey, or to add new ones mid-field as required.
    Add quota docs →

    Update Quotas#

    Adjust or remove quotas mid-field as needed. PATCH updates a quota's current target only - use PUT for any other changes.
    Update quota (PATCH) →
    Update quota (PUT) →
    Delete quota →

    Redirects & Hashing#

    PureSpectrum provides a robust yet easy-to-understand redirect and hashing mechanism to prevent abuse and fraud.
    Required
    All clients using the Buy API must implement redirects and hashing to protect our mutual systems.
    Redirects guide →

    Implementing Status & Reference Codes#

    PureSpectrum APIs use various status and reference codes - survey status, respondent status, localization, age units, and currency. Review these regularly and keep your mappings current.
    Status & Reference Codes docs →

    Registering Completes#

    We recommend using the "Register transaction as complete" endpoint as an extra verification layer alongside our hashing mechanism when redirecting respondents back to PureSpectrum.
    Registering completes docs →

    Reconciliation#

    PureSpectrum's reconciliation APIs let you update transaction status after client-side quality checks, so you can reject respondents that don't meet quality standards.
    Reconciliation endpoint docs →

    Production Access#

    Implementing the functionality within this document as described, makes gaining access to production quicker and easier.

    Diagram of flow for reference#

    Recommended API Flow.drawio (2).png
    Modified at 2026-11-03 15:46:30
    Previous
    Status Page
    Next
    Survey Status Codes