Skip to main content
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.