01Opportunity intake
Define the buyer-side conditions first.
Share the survey link, target market, audience, required completes, incidence, LOI, field timing and acceptance rules.
BriefAudienceRules
TargetingLOIIncidenceQuality rules
Survey API and managed sample
A controlled API layer for survey buyers and supply partners.
DATA-ORCHID supports B2C and selected B2B survey supply through source-tagged routing, partner/API access, PollsOpinion acquisition and quality-monitored traffic. Scale is discussed after a project-level review.
How the layer works
Move from opportunity intake to accepted-complete reconciliation.
The operating model connects source review, profile matching, router logic and buyer-side feedback into a single project conversation.
Buyer shares survey/router link, targeting, LOI, quotas and validation rules.
Traffic is tagged by source and sub-ID and reviewed against project requirements.
Eligible respondents are routed through relevant buyer opportunities.
Accepted completes, rejects and feedback inform future source decisions.
Managed sample
A managed route for buyers who want operational context.
Managed sample discussions cover the brief, market, audience, timing, quality rules and expected reconciliation before routes are activated.
02Source review
Choose the right supply path.
Potential sources include managed panels, PollsOpinion acquisition, affiliate partners, partner traffic and API routes. Suitability is reviewed per project.
PanelPollsOpinionReviewAffiliateAPI route
Panel accessPollsOpinionAffiliate trafficAPI partner
03Delivery loop
Use buyer feedback to manage the route.
Starts, screen-outs, completes, rejects and reconciliation feedback can be reviewed source-wise. No live delivery metric is implied.
StartReviewFeedback
Source IDsAccepted completesReject feedback
How to read this: each stage informs the next one. The diagram illustrates the operating conversation; it does not guarantee supply, delivery volume or acceptance.
Integration overview
Keep the technical conversation clear and contract-led.
The integration overview shows the information typically agreed during onboarding. Credentials, endpoints and field names are confirmed for each partnership.
POST /opportunity
{
"market": "agreed-market",
"source_id": "partner-sub-id",
"status": "project-review"
}
{
"market": "agreed-market",
"source_id": "partner-sub-id",
"status": "project-review"
}
01
Buyer integration
Discuss router links, status handling, targeting, acceptance and reconciliation.
02
Supplier integration
Discuss source tags, traffic quality, caps, validation and agreed commercial conditions.
03
Operational handoff
Document the agreed workflow before any production credentials or live endpoints are exchanged.
Ready to review a routing requirement?
Share the buyer brief or partner capability and we’ll direct it to the right conversation.