All roles
Research infrastructure

For Developers

Integrate research without guessing schemas: inspect capabilities, fail invalid studies before fielding, and keep credentials and delivery boundaries scoped.

Integration architecture
Validation and automation
Data handoff
Read API docsDiscuss an integration
Illustrative Gotopico decision report with evidence-linked recommendations, research charts, caveats, reviewer approval, and export controls.
Illustrative product view—not a customer result
Beta

A relevant product path

Turn findings into a reviewed decision report

For developers, start with question manifest: Read capability and schema contracts before rendering or generating an instrument.

Open the matched decision guide

Problems this playbook solves

Each path starts with a concrete decision, names the method, and links to the deeper problem guide.

Question manifest

Problem

Generated forms drift when clients guess supported question types and configuration.

How to solve it

Read capability and schema contracts before rendering or generating an instrument.

Capability manifest
Typed schemas
Open the decision guide
Readiness validation

Problem

Invalid logic and unsupported configuration should fail before a live survey reaches respondents.

How to solve it

Run deterministic readiness checks and surface actionable issues before publication.

Dry run
Readiness checks
Open the decision guide
Research data pipeline

Problem

Ad hoc exports and broad credentials make integrations brittle and hard to audit.

How to solve it

Use scoped API keys, webhooks, and reviewed export contracts for bounded integrations.

API keys
Webhooks
Open the decision guide

Survey examples

Three surveys for the decisions ahead

Start with the decision, inspect the evidence available today, and keep the limits attached to every handoff.

API-created pricing study

Trace a deterministic study from API request through survey and analysis objects.

API-created pricing study: public template setup preview. This is not an authenticated editor or respondent run.
Respondent Or Setup · Captured

Synthetic example · not a customer result.

Live execution is not certified.

Public: Beta

Boundary: Use synthetic credentials and documented plan limits.

Evidence gap: Authenticated local survey creation, text-question readiness correction and free-plan cap checks now pass. Pricing analysis and the illustrative /studies contract remain fixture-only; deployed execution is unverified.

Read API docsRead study evidence and limitations
How it works and evidence limits

Use this when

Documentation and product behavior drift apart.

What you do

Create a study, add questions, collect synthetic responses, and request analysis.

  • Correlated API objects
  • Deterministic synthetic responses
  • Documented limits and redaction

Evidence returned

Correlated request, survey, and result objects.

Product: Beta
Evidence: Seeded Capture Ready

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Capture: Public Template Setup. Live execution is not certified.

Inspect synthetic API evidence

Capabilities: scoped-api-keys, research-method-question-types

Read evidence provenance and downloads

Technical study evidence

Illustrative technical evidence using deterministic synthetic data. It is not a customer result, live connector receipt, or outcome claim.

Fixture version
technical-persona-evidence.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

All organizations, products, respondents, identifiers, results, and delivery acknowledgements are fictional.

Authentication and signing material is omitted or visibly redacted; these files contain no usable credentials.

Webhook and warehouse receipts validate fixture lineage only and do not prove a live connector, external delivery, retry policy, or signature verification.

No artifact is customer evidence, production availability evidence, a security claim, or an outcome claim.

Artifact downloads

v1/api/pricing-analysis.response.json

SHA-256: 5725bfb1ca16b5ec80eac28f0ffb296e6d06f1ce2eaa123693d338d1490d201e

v1/api/pricing-study.create.request.json

SHA-256: d16f54ecf1f711bc5ad265b720da8ae93e034ce42573ba988e4247f146b86d56

v1/api/pricing-study.create.response.json

SHA-256: 15b37a335e3dc2f1a240c867675b83b9beaf764e2abefe0420c0798290e6f45b

v1/api/readiness.corrected.request.json

SHA-256: 5e72f05df67846de9bbe574d18b0bd43610e7f18133e1fca2ad09dd493b82348

v1/api/readiness.corrected.response.json

SHA-256: a1db393eb97b2fa0c8269f121ffcc76ba3fb7f92191e383764a7ef7aa7c11ca4

v1/api/readiness.invalid.request.json

SHA-256: 62b7fea239ce80429cbc850afa429fa27c535f5d36f3647d5f2dfe405b9daba7

v1/api/readiness.invalid.response.json

SHA-256: 35e685f5ba33232141dcab3fde950d0b8de3023ed4f6e206df00dce50de97d9c

v1/audit/warehouse-delivery.json

SHA-256: 7faaeb848549cea440719bcc90eafba59dff2c5af481db8f3948f52bc48f6c90

v1/exports/readiness-survey.v1.json

SHA-256: 2a061a1e0120336af941ae36ef8e625b8994ae48e77b7cd47432d0b7d5823e2c

v1/exports/technical-responses.v1.csv

SHA-256: 9472d201249eaf5e8a8bd57dc6e2695aca67bbbe807e665859674c3825bd531a

v1/exports/technical-responses.v1.json

SHA-256: d49dbd1f5c3d76d2f79ab1b714b732e4991c2986f2b49d4ee406826fd22d58ea

v1/quality/quality-review.json

SHA-256: 0bfa8d0a6978bb84758f716e3cf19f36e77ba2cc60ae628e59b8ded8027f1b72

v1/reports/stakeholder-report.json

SHA-256: e2ecf76581a872a274d3316cadf8b7aa820bcf6d2ba864a83500ac2e00573657

v1/source/technical-responses.json

SHA-256: 73cf5f1ed401188b540b8de550788e95bc800cc48c95ae09d36f3703850ca374

v1/webhooks/response-exported.receipt.redacted.json

SHA-256: 5de2c0a520f1944982399f0cce0e2bfd5ed9f24f068759be1d7ddef66a07fd0a

v1/webhooks/survey-published.receipt.redacted.json

SHA-256: 8238f18ce232ab04a5cb2cc8e5c69703cc16d73efe99fad2478fe7bd24c0e615

Download machine-readable manifest

Embedded onboarding feedback

Test a responsive in-product feedback surface without overstating embed readiness.

Actual local respondent setup embedded by the repository SDK on an approved fixture parent; synthetic one-question study.
Respondent Or Setup · Captured

Synthetic example · not a customer result.

Live execution is not certified.

Public: Private Beta

Boundary: Private beta; this is not a general custom-domain or production-readiness claim.

Evidence gap: Local approved/denied parent checks, served CSP headers, finite SDK sizing, reviewed response completion and attributed response captures pass. The stored parent origin is client-reported and allowlist-checked; deployed infrastructure and general custom-domain readiness remain unverified.

Discuss embed betaRead study evidence and limitations
How it works and evidence limits

Use this when

Teams need in-product feedback without breaking layout, origin rules, or attribution.

What you do

Embed the approved respondent surface on a controlled fixture origin.

  • Controlled-origin embed
  • Responsive height behavior
  • Attributed response path

Evidence returned

Responsive rendering, resize behavior, and attributed response.

Product: Private Beta
Evidence: Beta Proof

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Capture: Authenticated Local Synthetic Product. Live execution is not certified.

Inspect technical evidence boundaries

Capabilities: basic-survey-logic-runtime, connections

Read evidence provenance and downloads

Technical study evidence

Illustrative technical evidence using deterministic synthetic data. It is not a customer result, live connector receipt, or outcome claim.

Fixture version
technical-persona-evidence.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

All organizations, products, respondents, identifiers, results, and delivery acknowledgements are fictional.

Authentication and signing material is omitted or visibly redacted; these files contain no usable credentials.

Webhook and warehouse receipts validate fixture lineage only and do not prove a live connector, external delivery, retry policy, or signature verification.

No artifact is customer evidence, production availability evidence, a security claim, or an outcome claim.

Artifact downloads

v1/api/pricing-analysis.response.json

SHA-256: 5725bfb1ca16b5ec80eac28f0ffb296e6d06f1ce2eaa123693d338d1490d201e

v1/api/pricing-study.create.request.json

SHA-256: d16f54ecf1f711bc5ad265b720da8ae93e034ce42573ba988e4247f146b86d56

v1/api/pricing-study.create.response.json

SHA-256: 15b37a335e3dc2f1a240c867675b83b9beaf764e2abefe0420c0798290e6f45b

v1/api/readiness.corrected.request.json

SHA-256: 5e72f05df67846de9bbe574d18b0bd43610e7f18133e1fca2ad09dd493b82348

v1/api/readiness.corrected.response.json

SHA-256: a1db393eb97b2fa0c8269f121ffcc76ba3fb7f92191e383764a7ef7aa7c11ca4

v1/api/readiness.invalid.request.json

SHA-256: 62b7fea239ce80429cbc850afa429fa27c535f5d36f3647d5f2dfe405b9daba7

v1/api/readiness.invalid.response.json

SHA-256: 35e685f5ba33232141dcab3fde950d0b8de3023ed4f6e206df00dce50de97d9c

v1/audit/warehouse-delivery.json

SHA-256: 7faaeb848549cea440719bcc90eafba59dff2c5af481db8f3948f52bc48f6c90

v1/exports/readiness-survey.v1.json

SHA-256: 2a061a1e0120336af941ae36ef8e625b8994ae48e77b7cd47432d0b7d5823e2c

v1/exports/technical-responses.v1.csv

SHA-256: 9472d201249eaf5e8a8bd57dc6e2695aca67bbbe807e665859674c3825bd531a

v1/exports/technical-responses.v1.json

SHA-256: d49dbd1f5c3d76d2f79ab1b714b732e4991c2986f2b49d4ee406826fd22d58ea

v1/quality/quality-review.json

SHA-256: 0bfa8d0a6978bb84758f716e3cf19f36e77ba2cc60ae628e59b8ded8027f1b72

v1/reports/stakeholder-report.json

SHA-256: e2ecf76581a872a274d3316cadf8b7aa820bcf6d2ba864a83500ac2e00573657

v1/source/technical-responses.json

SHA-256: 73cf5f1ed401188b540b8de550788e95bc800cc48c95ae09d36f3703850ca374

v1/webhooks/response-exported.receipt.redacted.json

SHA-256: 5de2c0a520f1944982399f0cce0e2bfd5ed9f24f068759be1d7ddef66a07fd0a

v1/webhooks/survey-published.receipt.redacted.json

SHA-256: 8238f18ce232ab04a5cb2cc8e5c69703cc16d73efe99fad2478fe7bd24c0e615

Download machine-readable manifest

Readiness-to-webhook pipeline

Show invalid input failing clearly before a corrected study emits a bounded event.

Readiness-to-webhook pipeline: public template setup preview. This is not an authenticated editor or respondent run.
Respondent Or Setup · Captured

Synthetic example · not a customer result.

Live execution is not certified.

Public: Beta

Boundary: Each connector retains its documented availability and limits.

Evidence gap: Authenticated local text-question readiness correction passes; versioned export, signed retry and receipt correlation pass local integration tests. Deployed worker and object-store delivery remain unverified.

Read API docsRead study evidence and limitations
How it works and evidence limits

Use this when

Invalid instruments launch and downstream events arrive without stable contracts.

What you do

Fail readiness, correct the payload, and inspect a bounded synthetic event contract.

  • Actionable readiness errors
  • Corrected publish state
  • Redacted delivery receipt

Evidence returned

Error codes, corrected state, delivery receipt, and export.

Product: Beta
Evidence: Seeded Capture Ready

Illustrative product view using synthetic data. It is not a customer result or outcome claim.

Capture: Public Template Setup. Live execution is not certified.

Inspect synthetic pipeline evidence

Capabilities: survey-readiness-dry-run, event-webhooks, agent-safe-research-loop

Read evidence provenance and downloads

Technical study evidence

Illustrative technical evidence using deterministic synthetic data. It is not a customer result, live connector receipt, or outcome claim.

Fixture version
technical-persona-evidence.v1
Declared fixture timestamp
Provenance
Checked-in deterministic synthetic fixtures. Hashes identify artifact contents; they do not certify live execution.

Limitations

All organizations, products, respondents, identifiers, results, and delivery acknowledgements are fictional.

Authentication and signing material is omitted or visibly redacted; these files contain no usable credentials.

Webhook and warehouse receipts validate fixture lineage only and do not prove a live connector, external delivery, retry policy, or signature verification.

No artifact is customer evidence, production availability evidence, a security claim, or an outcome claim.

Artifact downloads

v1/api/pricing-analysis.response.json

SHA-256: 5725bfb1ca16b5ec80eac28f0ffb296e6d06f1ce2eaa123693d338d1490d201e

v1/api/pricing-study.create.request.json

SHA-256: d16f54ecf1f711bc5ad265b720da8ae93e034ce42573ba988e4247f146b86d56

v1/api/pricing-study.create.response.json

SHA-256: 15b37a335e3dc2f1a240c867675b83b9beaf764e2abefe0420c0798290e6f45b

v1/api/readiness.corrected.request.json

SHA-256: 5e72f05df67846de9bbe574d18b0bd43610e7f18133e1fca2ad09dd493b82348

v1/api/readiness.corrected.response.json

SHA-256: a1db393eb97b2fa0c8269f121ffcc76ba3fb7f92191e383764a7ef7aa7c11ca4

v1/api/readiness.invalid.request.json

SHA-256: 62b7fea239ce80429cbc850afa429fa27c535f5d36f3647d5f2dfe405b9daba7

v1/api/readiness.invalid.response.json

SHA-256: 35e685f5ba33232141dcab3fde950d0b8de3023ed4f6e206df00dce50de97d9c

v1/audit/warehouse-delivery.json

SHA-256: 7faaeb848549cea440719bcc90eafba59dff2c5af481db8f3948f52bc48f6c90

v1/exports/readiness-survey.v1.json

SHA-256: 2a061a1e0120336af941ae36ef8e625b8994ae48e77b7cd47432d0b7d5823e2c

v1/exports/technical-responses.v1.csv

SHA-256: 9472d201249eaf5e8a8bd57dc6e2695aca67bbbe807e665859674c3825bd531a

v1/exports/technical-responses.v1.json

SHA-256: d49dbd1f5c3d76d2f79ab1b714b732e4991c2986f2b49d4ee406826fd22d58ea

v1/quality/quality-review.json

SHA-256: 0bfa8d0a6978bb84758f716e3cf19f36e77ba2cc60ae628e59b8ded8027f1b72

v1/reports/stakeholder-report.json

SHA-256: e2ecf76581a872a274d3316cadf8b7aa820bcf6d2ba864a83500ac2e00573657

v1/source/technical-responses.json

SHA-256: 73cf5f1ed401188b540b8de550788e95bc800cc48c95ae09d36f3703850ca374

v1/webhooks/response-exported.receipt.redacted.json

SHA-256: 5de2c0a520f1944982399f0cce0e2bfd5ed9f24f068759be1d7ddef66a07fd0a

v1/webhooks/survey-published.receipt.redacted.json

SHA-256: 8238f18ce232ab04a5cb2cc8e5c69703cc16d73efe99fad2478fe7bd24c0e615

Download machine-readable manifest
Role-specific workflow
1

Before integration: inspect the capability manifest and validate a representative payload.

2

Before production: constrain credentials, test retries and signatures, and document the data contract.

Decision-ready handoffs
OpenAPI contract
Manifest
Dry-run result
Webhook event
CSV/JSON export

Important context: Scoped API keys are a Professional capability; expanded Insight API endpoints and some connectors retain their documented beta or planned status.

Start Here Next

Templates

Launch from a tested template

Use a template when you need seeded demo states, stable payloads, and predictable QA before launch.

Browse templates
Resources

API and implementation docs

Review API docs, webhooks, and resource planning paths before connecting research data to your stack.

Open API docs
Trust

Check security and data controls

Review access, privacy, and governance expectations before sending respondent data through workflows.

Review trust

Related roles

Data analystsReceive analysis-ready survey data with stable structure, quality context, valid bases, suppression rules, and provenance preserved for downstream work.Product managersChoose the roadmap bet, package, or price with comparable customer evidence—not loudest-voice votes or a spreadsheet full of equal ratings.

Read the API docs

Discuss an integration

Read API docsDiscuss an integration