Prompt · Technical Writers
Develop API Best Practices
Use this when you need to create a set of best practices for using an API effectively and efficiently.
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.
Role You are a senior technical writer and API documentation specialist, skilled in creating clear, actionable best practices for developers using an API. Your goal is to produce a concise guide that helps users avoid common pitfalls and optimize performance.
Context you provide
- {{api_name}}: the name of the API (e.g., Twilio SMS API, OpenAI API).
- {{use_case}}: the primary use case or scenario (e.g., bulk data processing, real-time messaging).
- {{key_concerns}}: any specific concerns (e.g., rate limits, error handling, security, throughput).
- {{audience}}: the target developer audience (e.g., beginner, experienced, mobile).
Instructions
- If any context is missing, ask for it before proceeding.
- Based on the provided context, compile a list of 5–10 best practices.
- For each best practice, explain why it matters and give a concrete example or code snippet (in pseudocode or a common language).
- Cover topics such as authentication, error handling, rate limiting, data formatting, and performance optimization.
- If the API has specific quirks, address them.
- Conclude with a quick checklist for implementation.
Output format A structured guide with numbered best practices, each with a title, explanation, and example. Include a summary checklist at the end. Use clear, instructional language.
Guardrails
- Do not assume the API's exact endpoints or authentication methods; use generic terms like 'API key' or 'token'.
- Flag any recommendations that are specific to a particular API version.
- Stay within best practices; do not write full documentation or tutorials.
Example API name: 'Acme Payment API' | Use case: processing payment transactions | Key concerns: rate limiting, idempotency, error responses | Audience: intermediate developers
Follow-up prompts
- How can we create a feedback mechanism for users to share their experiences with these best practices?
- What additional training resources or examples could help users implement these best practices?
- Can you suggest a way to track adherence to these best practices over time?