Skip to content

Latest commit

 

History

History
19 lines (13 loc) · 891 Bytes

File metadata and controls

19 lines (13 loc) · 891 Bytes

📚 API Documentation

🛑 Essential

  • All public APIs must have OpenAPI documentation. Every public-facing API should be fully described using an OpenAPI specification (YAML or JSON). This guarantees clarity for consumers and supports integration, testing, and maintenance.

👍 Good To Have

  • Document internal APIs using OpenAPI. Where feasible, internal APIs should also be documented with OpenAPI specifications. This improves maintainability, supports onboarding, and helps prevent knowledge silos.

🏆 Luxury

  • Validate implementation against API specification. Use tools like league/openapi-psr7-validator or similar to test your implementation against the OpenAPI spec. Automated validation reduces drift between code and documentation and ensures long-term reliability.