Dynamic API Generation via Command Recording Metadata Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of a standardized API framework for every application leads to a significant burden on processing power, as each new application requires a new API framework, making it inefficient and resource-intensive, especially for repetitive processes where RPA processors have to develop repeated operations from scratch.

Innovation Solution

A system for dynamically generating APIs by extracting metadata from command recordings with start and end breakpoints, determining API parameters based on pre-existing frameworks, and using robotic process automation for authentication, allowing for efficient reuse of repetitive processes and parallel execution with other system processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a new API framework is created for every new application, then the application can have customized API services, but the processing power burden increases significantly

Engineering Contradiction:
ImproveAPI framework customizationVSAvoidprocessing power consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements a universal API framework that can serve multiple applications through dynamic configuration. Instead of creating dedicated API frameworks for each application, the system uses a single reusable framework that adapts to different applications by loading appropriate configuration files and metadata, thereby reducing processing power consumption while maintaining adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system performs preliminary actions by pre-defining API framework structures, metadata schemas, and configuration templates that can be reused across multiple applications. This allows the framework to be quickly instantiated for new applications without requiring complete recreation, thus reducing processing overhead.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If API services are provided for every application, then service coverage is improved, but the complexity of managing multiple API frameworks increases

Engineering Contradiction:
ImproveAPI service coverageVSAvoidAPI framework management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A single universal API framework manages multiple applications through standardized configuration mechanisms. The framework provides consistent service coverage across applications while simplifying management through unified configuration files, metadata extraction processes, and reusable template structures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses copying mechanisms by replicating configuration files and metadata structures from existing API frameworks to new applications. This allows rapid deployment of API services with minimal manual configuration, reducing management complexity while maintaining service coverage.

Inventive Principle:
Principle #26Copying

3Ease of operation

If RPA processors develop repetitive operations from scratch, then each operation is customized to specific needs, but time and processing efficiency are reduced

Engineering Contradiction:
Improveoperation customizationVSAvoidprocessing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system performs preliminary actions by extracting metadata from command recordings and pre-defining API parameter structures for repetitive operations. This allows RPA processors to reuse pre-configured operation templates rather than developing operations from scratch, significantly improving processing efficiency while maintaining customization through metadata-driven configuration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The API generation system performs self-service by automatically extracting metadata from command recordings and generating appropriate API configurations without requiring manual intervention for each repetitive operation. This automation improves processing efficiency while maintaining operation customization through intelligent metadata analysis.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12175307B2System and method of automated processing for dynamic API generation
Publication Date: 2024.12.24 BANK OF AMERICA CORP
  • US12175307B2 patent drawing
  • US12175307B2 patent drawing
  • US12175307B2 patent drawing

AI summary

Various systems, methods, and computer program products are provided for dynamically generating an API. The method includes extracting metadata from a command recording of a system API. The command recording of the system includes a starting breakpoint and an ending breakpoint for one or more repetitive processes. The method also includes determining one or more API parameters for an API to be generated based on the extracted metadata. The method further includes dynamically generating the API based on the API parameters. The method still further includes causing an authentication of the credentials relating to the API via robotic process automation.