API Schema Mapping via Directed Graphs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating external APIs with internal APIs is cumbersome due to differences in schema organization, entity naming, and operations, requiring significant effort and being prone to errors as the number of APIs increases.

Innovation Solution

A computer-implemented method that maps internal API schema properties to external API schema properties using directed graphs and semantic representations, generating computer code to perform external API calls, thereby automating the integration process and reducing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual integration methods are used to integrate external APIs with internal APIs, then integration can be achieved, but the effort and time required increase significantly

Engineering Contradiction:
Improveintegration speedVSAvoidintegration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining schema mappings between internal and external API properties before actual integration is needed. The directed graph is constructed in advance with nodes representing schema properties and edges representing mapping relationships, so that when integration is required, the system can quickly query the pre-established graph rather than creating mappings from scratch each time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary component - the directed graph - that mediates between internal API schemas and external API schemas. This graph acts as a translation layer that automatically resolves mapping relationships between different schema organizations, entity names, and operations, eliminating the need for manual integration work while maintaining accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual integration methods are used to integrate external APIs with internal APIs, then integration can be achieved, but error rates increase due to the complexity and volume of work

Engineering Contradiction:
Improveintegration accuracyVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The directed graph serves as an intermediary that systematically manages the complexity of API integration. By representing schema properties as nodes and mapping relationships as edges, the graph provides a structured, visual, and computable model that reduces integration complexity and minimizes errors through automated pathfinding algorithms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual mechanical integration work with automated computational processes. Instead of manually mapping each schema property and tracking relationships, the system uses computer algorithms to traverse the directed graph and generate integration code automatically, thereby reducing human error and improving reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If the number of APIs to integrate increases, then more functionality is available, but the effort and resources required for integration increase disproportionately

Engineering Contradiction:
ImproveAPI integration capabilityVSAvoidintegration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The directed graph approach provides a universal integration framework that can handle multiple different external APIs through a single consistent methodology. The same graph construction and query mechanisms work regardless of which external APIs need to be integrated, making the system versatile and scalable without requiring separate integration processes for each API.

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

Solution Approach 2:

The patent segments the integration problem into discrete, manageable components represented as nodes in the directed graph. Each schema property becomes an independent node, and mapping relationships become independent edges. This segmentation allows the system to handle complex multi-API integrations by breaking them down into smaller, tractable sub-problems that can be solved through graph traversal.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11537448B1Adapting application programming interfaces with schema mappings
Publication Date: 2022.12.27 ASAPP INC
  • US11537448B1 patent drawing
  • US11537448B1 patent drawing
  • US11537448B1 patent drawing

AI summary

A first application programming interface (API) with a first schema may be adapted to work with a second API with a second schema using mappings of schema properties and a directed graph. An API call specification of the first API may receive first API schema properties as input and provide first API schema properties as outputs. The first API schema properties may be mapped to corresponding second API schema properties, such as using semantic representations of the schema properties. An implementation of an API call for the first API may be created by using the schema mappings and selecting a path from a directed graph corresponding to the second API, where the path includes a node corresponding to an API call of the second API. Computer code may be generated using nodes of the path, and the computer code may be stored for later use.