From a question
to a research request.

1. Get your API key.

Request access from Gather. Store the key as GATHER_API_KEY in your server environment. Do not expose it in client-side JavaScript, URLs, screenshots, or public repositories.

The published API uses bearer-token authentication and JSON request bodies.

2. Define the question and audience.

curl https://synthetic.gatherhq.com/api/v1/studies \
  -H "Authorization: Bearer $GATHER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "What makes IT buyers switch?",
    "study_type": "messaging",
    "audience_description": "IT leaders at mid-market companies"
  }'

topic defines what you want to understand. study_type selects the research category. audience_description describes the people the study should concern.

Published study types include brand, product, concept, competitor, cx, pricing, messaging, winloss, churn, segmentation, and custom. Query GET /api/v1/study-types for available values.

3. Work with the research.

Gather’s published examples include headline_finding, key_findings, consensus_themes, objections, and report_url. Use those concepts to design an experience that puts the finding and its implications ahead of implementation details.

A webhook_url can be included in the published study request pattern. Confirm the delivery contract and verification requirements with Gather before enabling an automated receiver. GET /api/v1/studies/{id} retrieves an individual study.