API Interoperability via Workflow Chaining and Classification Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current APIs are limited to servicing a single type of response based on a single request, leading to inefficiencies and delays as internal users need to access multiple applications for day-to-day operations, with API data structured in an ad hoc manner.
Innovation Solution
A system and method for API interoperability that allows users to chain multiple APIs together by registering them with a classification protocol, identifying sequences of rules to generate workflows, and saving these workflows for later execution, enabling APIs to perform multiple operations without requiring users to visit multiple applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If APIs service only one type of response based on a single request, then API simplicity is maintained, but user productivity and operational efficiency deteriorate due to needing to access multiple applications
Solution Approach 1:
The patent implements a universal API framework where a single API can service multiple types of responses and operations through workflow chaining. The system allows APIs to be composed into sequences that handle complex multi-step operations, transforming single-function APIs into multi-functional service units without requiring users to access multiple separate applications.
Solution Approach 2:
The patent segments complex operations into discrete API calls that can be chained together in workflows. By breaking down multi-step business processes into individual API operations that can be sequentially executed, the system enables a single API interface to handle what would traditionally require multiple separate applications, thereby improving productivity without proportionally increasing complexity.
2Adaptability or versatility
If users access multiple applications for day-to-day operations, then specific business needs can be addressed, but time consumption and operational delays increase
Solution Approach 1:
The patent merges multiple API operations into unified workflows that can be executed through a single API interface. By combining sequential API calls, data transformations, and business logic into integrated workflow units, the system consolidates what would traditionally require multiple separate application accesses into a single coordinated operation, reducing time consumption while maintaining full business capability.
Solution Approach 2:
The patent implements preliminary action by pre-defining and storing workflow sequences that chain multiple API operations together. These pre-configured workflows can be triggered with a single request, eliminating the need for users to manually execute multiple separate API calls or switch between applications, thereby significantly reducing operational time while maintaining adaptability to various business needs.
3Ease of manufacture
If APIs are structured in an ad hoc manner, then implementation flexibility is maintained, but system reliability and interoperability deteriorate
Solution Approach 1:
The patent applies parameter changes by establishing standardized parameters and interfaces for API workflows while maintaining flexibility in workflow composition. The system defines standard parameters for API registration, workflow configuration, and execution, which ensures reliable interoperability between different APIs. At the same time, the standardized framework allows flexible implementation of various business logic sequences, achieving both reliability through standardization and flexibility through configurable workflow composition.
Data Source
AI summary
The invention relates to providing API interoperability. An embodiment of the present invention is directed to increasing API productivity by chaining (or sequencing) APIs together to accomplish multiple operations. The innovative system enables APIs to be strung together, in a way that eliminates or reduces a user's need to visit and/or invoke multiple applications and/or APIs. An embodiment of the present invention is directed to expanding a traditional usage of point-to-point API invocation. The innovative system may define a classification protocol to enable API providers and/or creators to register an API by a command type (e.g., entitlement, query, data, etc.). Each command type may have a minimum set of mandatory operations that an API may be required to expose. By adhering to the contract, APIs may be handled generically, without knowing which system and/or app created the API.