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)
    • 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
  1. Guides

Integrations Process

To assess whether PureSpectrum Buy API answers your online sample needs, start with a review of our Buy API Documentation.
Do not hesitate to get in touch with your PureSpectrum representative for any questions that you might have.

šŸš€ Getting Started#

Why integrate with our Buy API?
Use your own system/UI to program your survey
Automation of repetitive tasks and workflows
Improved efficiencies, by removing manual tasks, reducing errors and increasing productivity
Scalability, to keep up with your growing business
Authorisation:
API access requires the authorization parameter in the request header.
You will receive different keys for Production and Staging.
You can create and a launch a survey, in two single API calls by following the steps below:

1
Create survey
Create survey
2
Take survey live
Take survey live
Other useful guides:
Buyer Redirect Guide
Link Security Hashing

āš™ļø The Process
#

1
Discovery
We start with a kick-off call where both Commercial and Technical representatives on the PureSpectrum and Client side cover the non-exhaustive list below:
1.
The various use cases for testing the Buy API
2.
Your development timeline for integrating our API
3.
API or hybrid (both UI & API) preference
4.
A demo of the system you'll be integrating with the API
5.
Phased development or trying all the features at once? If phased, which are the initial features required and which would be adopted later?
6.
List of users who require access to the Staging environment
7.
Preferred communication channel, Email or Slack?
8.
Agreed cadence, to monitor progress
9.
Any other helpful information that might ease the process
2
Staging Access
You are granted access to our Staging environment, for testing all available features. Staging login accounts are created for the confirmed users.
A staging access token is necessary to test all endpoints.
Make sure your testing in Staging covers the points below, as a minimum. We will check your test surveys before granting you access to Production:
Usage of the feasibility endpoint to check feasibility and recommended price, without creating a survey
Correct survey setup based on various qualifications, quotas, and price
Inbound and outbound hashing of redirects
3
Go-Live Testing
Verifying that hashing and redirects are set up correctly and working
Testing of survey lifecycle management (survey creation, updating, transitioning through statuses)
Respondent status is coming back to PureSpectrum with the correct status
Audiences & Quotas are being defined correctly, and in line with your expectations
The consumption of feasibility and subsequent defining of CPI
Updating transactions and reconciliation
4
Production Access
Once the PureSpectrum SaaS agreement has been signed and we have successfully checked your test survey setups, redirects, and hashing, you get access to our Production environment.
A Production access token is necessary to use all endpoints.
If you are currently a user of the UI, please let us know whether you prefer to use the same account for API calls or require a distinct account.
It is recommended to use a separate API account to maintain a clear distinction between API and UI surveys.
We can arrange a meeting, or a recurring cadence, to review your API integration and address any questions, concerns, or optimization options.
5
Monitor and Review Real Surveys in Production
API Agreement is signed
Production API Key & login credentials provided
Soft launch and monitor small-sample sizes across a few surveys
Review survey results and full launch
6
Optimize: Performance Recommendations and New Features
PureSpectrum makes recommendations for API optimization
Integration enhancements by the customer
New features / API endpoints communicated on an ongoing basis
There are a few differences between our Staging and Production environments:
Different API keys
Different attributes
Different qualification codes
Dummy prices on staging
Dummy feasibility on staging
Dummy suppliers on staging
No real traffic on staging

Getting Started with the API#

PureSpectrum Buy APIs are a suite of REST endpoints, purpose-built for secure, fast, and easy access.
Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

āœ… Requirements#

For a straightforward interaction with our Buy API, consider the following as minimum requirements:
A PureSpectrum Buy API account
API key or authentication credentials with appropriate permissions
Basic understanding of programming, API consumption, and JSON schema
Familiarity with HTTP methods (GET, POST, PUT, DELETE) and status codes
Ability to handle API error codes
Secure storage of API credentials to prevent unauthorized access
Compliance with any applicable data privacy and security policies
Understanding of response formats and how to parse relevant data for business needs

API Versions#

There are two API versions, v2 and v3. Currently, v2 is mostly in use; some endpoints also use v3.

Test It Out#

šŸ•¹ Test it out
To get going quickly, we recommend using an API collaboration tool (e.g. Postman, Apidog). You can also use this documentation to try our collection of endpoints directly within your browser, using the Try it button and your Staging token on each endpoint page. All testing done via the Try it button will be reflected in your PureSpectrum Staging account.
Expected Timelines (assumes 2-week sprints and 1-2 developers on the project)
Survey TypeBuildGo LiveOptimization
Simple surveys (basic qualifications and quotas)2 - 4 weeks4 - 10 weeks1 - 2 weeks
Complex surveys (advanced targeting, complex quotas)4 - 8 weeks8 - 16 weeks2 - 4 weeks
Enterprise-level integrations6 - 18 weeks10 - 20 weeks2 - 6 weeks

šŸ“ Changelog#

Introducing a new endpoint? Updating an existing one? Deprecating or announcing a breaking change? It's all in the Changelog page.
The Changelog lets users view new releases, updates, and critical changes to all APIs — an easy way for developers to stay up to date with the latest changes to the Buy API.
Modified atĀ 2026-09-03 16:00:39
Previous
Real-Time Notifications (SNS)
Next
API Reference