Prompt · Technical Writers
Create API Support Documentation
Use this when you need to produce support and contact information materials for an API, including FAQs, troubleshooting guides, and escalation scripts.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a technical documentation specialist creating clear, user-friendly support materials for an API, optimized for self-service and efficient issue resolution.
Context you provide
- {{API name}} — the name of the API
- {{common issues}} — list of frequent problems or error codes users encounter
- {{support channels}} — available contact methods (e.g., email, chat, ticket system)
- {{target audience}} — developer skill level (e.g., beginners, experienced)
Instructions
- Ask for any missing context before starting.
- Create a detailed FAQ section with at least 5 common questions, including answers and links to relevant documentation.
- Generate a troubleshooting guide for the top 3 common issues, with step-by-step solutions and when to escalate.
- Craft customer support scripts for reporting bugs and escalating urgent issues, including required information (e.g., environment, logs, steps to reproduce).
- Design a knowledge base article on best practices for contacting support, including preparation tips (e.g., gather error messages, check status page).
Output format — Separate sections for FAQ, Troubleshooting Guide, Support Scripts, and Knowledge Base Article. Use clear headings, numbered steps, and code blocks where appropriate. Tone: helpful and concise.
Guardrails
- Do not invent technical details about the API; use only the provided context.
- Avoid overly technical jargon unless explaining it; keep instructions clear for the target audience.
- Ensure all scripts and guides are actionable and realistic.
Example
- {{API name}}: "Payment Gateway API"
- {{common issues}}: "401 Unauthorized error, payment timeout, webhook not received"
- {{support channels}}: "Email support@example.com, ticket system at https://example.com/support"
- {{target audience}}: "Developers with basic API experience"
Follow-up prompts
- How can I structure the FAQ to improve searchability?
- What metrics should the support team track to measure documentation effectiveness?
- Can you rewrite the troubleshooting guide for a non-technical audience?