Dynamic API Endpoints for Secure and Flexible Data Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy APIs with static endpoints are vulnerable to attacks, limiting developers' ability to update or experiment with new features, and lack flexibility in handling diverse user requirements, leading to data security issues and restricted data transactions.
Innovation Solution
A computer-implemented method and system that generates unique, dynamic endpoints for data transactions, allowing real-time validation and time-bound interactions with candidate application servers, enhancing security and enabling incremental testing of new code versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If static endpoints are used for API calls, then the system structure is simple and easy to implement, but the endpoints become easy targets for attackers leading to data security issues
Solution Approach 1:
The patent transforms static endpoints into dynamic endpoints that are generated in real-time based on user credentials and device information. Each endpoint is unique, time-bound, and automatically invalidated after use or expiration, making the system adaptive and secure against attacks while maintaining implementation feasibility through automated generation processes
Solution Approach 2:
The patent introduces an intermediary component that generates and manages dynamic endpoints between the user and the target system. This intermediary layer acts as a security buffer, preventing direct exposure of the target system to external attacks while still allowing legitimate authenticated users to access resources through generated endpoints
2Stability of the object's composition
If there is only one version of legacy code available, then system stability is maintained, but developers cannot experiment with new features or bug fixes in production environment
Solution Approach 1:
The patent segments the codebase into multiple isolated versions (legacy code and new code) that can coexist independently. Each version can be tested and validated separately through dynamic endpoint routing, allowing developers to experiment with new features in production while maintaining the stability of the legacy system through controlled traffic distribution
Solution Approach 2:
The patent uses parameter changes in endpoint generation to route requests to different code versions. By modifying endpoint parameters based on user credentials, device information, and routing rules, the system can dynamically direct traffic to legacy or new code versions, enabling flexible experimentation without compromising overall system stability
3Ease of operation
If static endpoints are exposed to external environment, then accessibility is improved, but endpoints are prone to attacks including man-in-the-middle attacks
Solution Approach 1:
The patent implements disposable, short-lived dynamic endpoints that are generated for specific transactions and automatically invalidated after use or expiration. Each endpoint is unique and cannot be reused, making the system accessible while preventing attackers from intercepting or replaying requests through man-in-the-middle attacks, as each endpoint becomes obsolete after a single use or time period
Data Source
Figure 1
Figure 2A
Figure 2B~2C
AI summary
The present disclosure relates to Application Programming Interface (API) framework that discloses a computer implemented method, polling service system, and non-transitory computer readable medium for providing dynamic endpoints for performing data transactions with a corresponding candidate application server. The method has two phases: a polling phase and a transaction phase. In the polling phase, the polling service system receives a first API request from one or more source devices and provides a dynamic endpoint for the one or more source devices to interact with the corresponding candidate application server of their requirement. In the transaction phase, the corresponding candidate application server receives a second API request from the one or more source devices through the dynamic endpoint generated during the polling phase, and performs data transactions.