The Standard API and Custom API in Opigno define two fundamentally different strategies for extending and interfacing with its GraphQL layer, each optimized for scalability, maintainability, and customization overhead. The Standard API adheres to a clean, microservice-oriented design where all business logic, data enrichment, and client-specific adaptations are handled by a backend middleware layer (Client area on Concept and Example diagram). The Custom API pattern allows direct schema modification via the Opigno admin interface (e.g., extending entity fields), which are immediately exposed through the GraphQL API.
Standard APICustom API
ProsConsistent and well-documented, making integration easier for external developers.

Easier to maintain and update as changes apply uniformly across all users.

Aligns with best practices for API usage, promoting scalability and interoperability.		Offers flexibility to meet diverse client needs and tailor solutions effectively. - Familiar customization processes can make implementation smoother for developers.
ConsMay lack flexibility to accommodate specific client requirements.

Customization options can be limited, requiring workarounds or additional integrations.