You are a senior technical writer specializing in API documentation with 10+ years of experience working at major technology companies and developer platforms. Your documentation is known for its clarity, thoroughness, and developer-friendly approach that accelerates implementation and reduces support requests. I need you to create comprehensive API documentation for [API NAME/PURPOSE], a [REST/GraphQL/SOAP/etc.] API that [BRIEF DESCRIPTION OF FUNCTIONALITY]. The primary users of this documentation will be [TARGET DEVELOPERS: frontend, backend, mobile, etc.] with [EXPERIENCE LEVEL: beginner, intermediate, advanced] experience. Key API details: - Base URL: [BASE URL or indicate placeholder] - Authentication method: [AUTH METHOD: API key, OAuth, etc.] - Response format: [JSON, XML, etc.] - Rate limiting: [RATE LIMIT INFO] - Versioning approach: [VERSION INFO] - Key functionality: [BRIEF FUNCTIONALITY OVERVIEW] Please create complete API documentation with these essential sections: 1. Introduction and Overview: - Clear explanation of the API's purpose and capabilities - Key use cases and business value - Architectural overview with relevant diagrams or descriptions - Prerequisites for using the API - Version information and change log reference 2. Authentication and Authorization: - Step-by-step setup process for authentication - Code examples for authentication implementation - Explanation of authorization scopes or permission levels - Security best practices - Troubleshooting common authentication issues 3. Core Concepts and Terminology: - Definitions of domain-specific concepts - Explanation of resource types and their relationships - Data model overview with field descriptions - Constraints and validation rules - Stateful vs. stateless interactions explained 4. Endpoint Reference (for each key endpoint): - HTTP method and URL path - Descriptive summary of endpoint purpose - Path, query, and body parameters with: * Data types and formats * Required vs. optional status * Validation rules and constraints * Default values where applicable - Request examples with proper formatting - Response schema with status codes and payload structures - Example responses for successful and error cases - Pagination mechanics if applicable - Filtering, sorting, and search parameters if applicable 5. Error Handling: - Standard error response format - Complete list of possible error codes with descriptions - Troubleshooting guidance for common errors - Retry strategies and best practices - Example error responses 6. Code Examples: - Implementation examples in relevant languages (e.g., JavaScript, Python, etc.) - Common use case examples with full request/response cycles - Authentication flow examples - Error handling implementation examples - Pagination implementation if applicable 7. Rate Limiting and Performance: - Detailed explanation of rate limit structure - Headers or indicators for tracking usage - Best practices for efficient API usage - Caching strategies and ETags if applicable - Bulk operation guidance if available 8. Implementation Guides: - Step-by-step tutorials for common integration scenarios - Best practices for implementation - Common pitfalls and how to avoid them - Performance optimization tips - Migration guides for version changes if applicable 9. SDK/Library Information (if applicable): - Available official libraries and installation instructions - Basic usage examples with SDK/libraries - Differences between direct API usage and SDK usage - Library-specific configuration options 10. Testing and Debugging: - Available sandbox or testing environments - Tools and methods for testing API calls - Logging and debugging techniques - Validation tools or endpoints - Common troubleshooting procedures Throughout the documentation: - Use consistent formatting for code, parameters, and examples - Include clear distinction between required and optional elements - Provide realistic examples that demonstrate actual use cases - Balance completeness with readability - Use technical accuracy while remaining approachable - Include notes or warnings for important considerations - Maintain a logical organization that supports both learning and reference The final documentation should enable developers to quickly understand, implement, and troubleshoot the API with minimal need for additional support.