{
  "title": "API documentation feedback survey",
  "questions": [
    "Which example was difficult to follow?",
    "What prerequisite was missing?",
    "What response detail needed explanation?"
  ],
  "question_notes": [
    "A difficult example identifies the documented step or assumption readers could not follow. Use synthetic request context and avoid collecting credentials or private payloads.",
    "A missing prerequisite identifies setup context required before a documented API step can be attempted. Add verified conditions and synthetic examples, without requesting credentials or presenting untested code as a supported integration.",
    "A response detail needing explanation identifies output meaning or handling missing from the documentation. Add verified synthetic examples without presenting untested behavior as supported."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Optional short text",
      "reason": "Retain the specific point or condition described; avoid replacing it with an unexplained rating."
    },
    {
      "question": 2,
      "format": "Optional written explanation",
      "reason": "Keep context that distinguishes different experiences. Never request API keys or credentials."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Add complete synthetic request and response examples."
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "note": "Examples to adapt. Not a validated instrument."
}
