PureSpectrum
PureSpectrum websiteHelp center
PureSpectrum websiteHelp center
    • 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

    HTTP Status Codes

    PureSpectrum applies the technical standards of the REST principles.
    Generally: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.). Codes in the 5xx range indicate an error with PureSpectrum’s servers (these are rare).
    Do not rely on individual status codes for determining overall success / failure of a request. The success status code may change depending on the content of the response or the action taken by the server.
    It's good practice to accept any success code as a successful response. You may still implement response handlers for individual status codes but only after a success/failure check has been performed.
    So, developers can always receive, read, decode, or understand the errors in responses based on the following form:
    ResponseStatusMeaning
    200SuccessThe request has succeeded.
    201CreatedAPI call has been accepted for processing. The sent resource has been successfully inserted/updated at our database.
    PureSpectrum Buy APIs may return the following error codes in response to any request encountering an error.:
    ResponseStatusMeaning
    400Bad RequestInvalid parameters, fields or filters.
    401UnauthorizedAuthorization error (invalid basic auth data or API key).
    403ForbiddenUnauthorized errors.
    404Record Not FoundSurveys or other data is not found.
    500Server ErrorsSomething went wrong on PureSpectrum’s end. (these are rare)
    Modified at 2026-03-05 20:08:28
    Previous
    Changelog
    Next
    Survey Status Codes