1. Buyer API
  • Supplier API
    • Supplier API – FAQ
    • HTTP Status Codes
    • --- Start Here ---
      • Onboarding Process
      • Mapping
      • Survey Inventory Management
      • Respondent-Survey Flow
      • Statuses, Term Reasons & Categories
      • Onboarding Checklist
      • API Call Flow
      • Frequently Asked Questions (FAQ)
      • Complete Validation Notifications
    • --- APIs ---
      • Lookup Question Library
      • Set Global redirect URLs and Pixels for supplier’s
      • Delete Global redirect URLs and Pixels for supplier’s account
      • Core Metadata Fields
      • Get Question Categories
      • Get Allocated Surveys (all live surveys)
      • Get Allocated Surveys By Id
      • Get Allocated Surveys By Date (live surveys only)
      • Get Allocated Surveys With Pagination (live surveys only)
      • Get Redirect Method for Survey
      • Set Redirect Method for Survey
      • Delete Redirect Method for Survey
      • Get Closed Survey List (allocated to supplier only)
      • Get Survey Transactions data
      • Get Survey Transactions data By Date Range
      • Survey Allow for Unique IP
      • Allow Unique PID & IP
      • Get Panellist Profiling
      • Survey Availability Endpoint
      • Get Survey Stats data By Date Range
      • Get Questions By Category
      • Answer Lookup
      • Get Survey Transactions data By PID and survey number
      • Get PIDs for re-contact surveys (studies)
      • Get survey stats
      • Set Panellist Profiling
      • update Panellist Profiling
      • get surveys for respondent
      • Respondent Pre Survey Check
      • Single Term Reason Category Code
      • term reason category
      • Get Allocated High Priority Surveys(All Live Surveys)
      • Get Survey Targeting
      • Get Quota for Survey
  • Buyer API
    • Buyer API - FAQ
    • API Call Flow
    • Create Job
      POST
    • Update Job
      PUT
    • Get Job Details
      GET
    • Core Metadata Fields
      GET
    • Update Job Status
      PUT
    • Get Job List By Status
      POST
    • Create Group
      POST
    • Update Group
      PUT
    • Get Group Details
      GET
    • Update Group Status
      PUT
    • Add Target to group
      POST
    • Update Target to group
      PUT
    • Remove Target Question
      DELETE
    • Add Quota to Group
      POST
    • Update Group Quota
      PUT
    • Get Group Quotas
      GET
    • Get Group Feasibility
      GET
    • Feasibility (Find estimates)
      POST
    • Questions Library
      GET
    • Get Job Stats
      GET
    • Get Group Stats
      GET
    • Get Group Quota Stats
      GET
    • Add Recontact to Group
      PUT
    • Get Recontacts of Group
      GET
  • Text Analyzer API
    • Text Analyzer API - FAQ
    • API Details
  • Postbacks/Redirects
    • Redirect URL
    • PostBack URL
    • Hashing Mechanism
    • Redirect URL Helper
  • View Change Log
    • View Change Log
  • Schemas
    • Sample Schemas
      • Pet
      • Category
      • Tag
  1. Buyer API

API Call Flow

Buyer API – Call Flow#

This document provides a complete overview of the Buyer API workflow to create, configure, validate, and launch a survey project (Job) on InnovateMR.
This is a project-driven integration, where your system is responsible for setting up demand, and InnovateMR handles respondent supply and delivery.

Overview#

The Buyer API flow consists of the following major stages:
1.
Job Creation (Project Setup)
2.
Group Creation (Segmentation)
3.
Targeting Setup
4.
Quota Setup
5.
Feasibility Validation
6.
Project Launch (Go Live)
7.
Monitoring & Optimization

End-to-End Flow#


1. Create Job#

API: Create Job
Create a new project (job) which acts as the top-level entity for the entire survey setup.
Key required fields include Name (Job Name), Project Manager / Sales Representative details, Start & End Dates, and Project Status.
Additional configurations like fingerprinting, duplicate checks (IP/PID), and security settings can also defined at this stage.

2. Create Group#

API: Create Group
Create a group under a job to define a survey segment with its own targeting and quotas.
Key required fields include Group Name, sample size (N), Incidence Rate, LOI, Estimated Cost, Country, and Survey URLs (Live/Test).
You also define basic targeting like country, language, and device type at this stage.

3. (Optional) Fetch Metadata#

API: Metadata / Mapping APIs
Retrieve platform-level metadata such as countries, languages, job types, group types, device types, and survey statuses required for configuration.
These values are used for mapping and standardizing inputs across job, group, and targeting setup.
This step ensures your system aligns with InnovateMR’s accepted values before applying targeting or quotas.

4. Set Targeting#

API: Add Targeting
Define audience targeting criteria for a group using predefined survey questions and options.
Key required fields include GroupId (path param), QuestionId, and Options (selected values or ranges).
This step directly controls who qualifies for the survey and impacts feasibility and delivery.

5. Set Quotas (Optional)#

API: Create Quotas
Define quotas within a group to control how completes are distributed across specific audience segments.
Key required fields include GroupId, Quota Title, N (sample size), and Conditions (targeting rules like age, gender, etc.).
This step ensures balanced sampling and prevents over-delivery for specific segments.

6. Check Feasibility#

API: Feasibility
Evaluate whether the defined group targeting can achieve the required completes and timelines.
Key input typically includes GroupId along with targeting, LOI, IR, and sample size (N) to estimate available supply.
This step is critical to ensure your setup is deliverable before making the job live.

7. Optimize (If Needed)#

API: Update Targeting / Update Quota / Update Group
Adjust targeting, quotas, or pricing based on feasibility results.
Repeat feasibility check until the setup is optimal.

8. Make Project Live#

API: Update Job Status and Update Group Status
Activate the project by updating both Job and Group status to LIVE, enabling the survey to start receiving traffic.
Key required fields include JobId / GroupId and Status (LIVE) to move entities from draft to active state.
This step marks the transition from setup to active data collection.

9. Monitor Performance#

API: Job Stats / Group Stats / Quota Stats
Track survey performance at job, group, and quota levels to monitor progress and delivery.
Key metrics include completes, conversion rates, incidence, and quota fulfillment status.
Monitoring helps in optimizing live projects for better results.
Modified at 2026-05-05 16:25:08
Previous
Buyer API - FAQ
Next
Create Job
Built with