Endpoint management system providing an application programming interface proxy service

• US 10,623,476 B2
• Filed: 03/23/2018
• Issued: 04/14/2020
• Est. Priority Date: 04/08/2015
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Thompson, Jonathan Paul
• Primary Examiner(s): Meky, Moustafa M
• Assistant Examiner(s): Waugh, Thorne E
• Application Number:
  US15/934,733
• Publication Number:
  US 20180309819A1
• Time in Patent Office: 753 Days
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

An endpoint management and proxy system is described, by which users can manage and enable exposure of application programming interfaces (“APIs”) usable to cause execution of program code on a remote or third party system. Systems and methods are disclosed which facilitate the handling of user requests to perform certain tasks on remote systems. The endpoint management system allows the application developer to define and specify a first proxy API which maps to a second API associated with the remote system. The endpoint proxy system receives requests to execute the proxy API, determines the API mapping, and sends one or more backend API requests to execute program codes by the associated remote systems. Responses from the remote systems are received by the endpoint proxy system which parses and/or transforms the results associated with the response and generates an output result for response back to the user computing systems.

Claims

1. A system, comprising:

one or more processors; and

one or more memories, the one or more memories having stored thereon instructions, which, when executed by the one or more processors, configure the one or more processors to;

maintain application programming interface (API) mapping definitions that map a plurality of proxy APIs to a plurality of backend APIs associated with a backend system;

receive an API mapping request to create a mapping between a first proxy API and a first backend API, the API mapping request including at least (i) one or more proxy API parameters associated with the first proxy API and (ii) one or more backend API parameters associated with the first backend API;

update the API mapping definitions such that the API mapping definitions include the mapping between the first proxy API and the first backend API, the updated API mapping definitions configured to cause execution of the first backend API in response to requests to execute the first API proxy;

receive a proxy API execution request to execute the first proxy API;

in response to the proxy API execution request to execute the first proxy API, determine, based on the updated API mapping definitions, that the first proxy API is mapped to the first backend API; and

transmit to the backend system a backend API execution request to execute the first backend API on the backend system.

2. The system of claim 1, wherein the one or more proxy API parameters include one or more of a function name associated with the first proxy API, an input parameter associated with the first proxy API, or an output parameter associated with the first proxy API.

3. The system of claim 1, wherein the one or more proxy API parameters specify a proxy output format in which a result of executing the first proxy API is to be provided.

4. The system of claim 1, wherein the one or more backend API parameters include one or more of a function name associated with the first backend API, an input parameter associated with the first backend API, or an output parameter associated with the first backend API.

5. The system of claim 1, wherein the one or more backend API parameters specify a backend output format in which a result of executing the first backend API on the backend system is to be provided.

6. The system of claim 1, wherein the API mapping request further includes a cache parameter for setting a duration for maintaining a cached result associated with executing at least one of the first proxy API or the first backend API.

7. The system of claim 1, wherein the API mapping request further includes a security parameter for limiting access to at least one of the first proxy API or the first backend API.

8. The system of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to, in response to a request to update the API mapping definitions, output a warning based on a determination that the requested update would disrupt an existing mapping in the API mapping definitions between a proxy API and a backend API.

9. The system of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to provide a user interface to a user computing device in network communication with the system, wherein the user interface allows a user of the user computing device to specify the one or more proxy API parameters and the one or more backend API parameters.

10. The system of claim 9, wherein the user interface is presented in one of a web page, a mobile application display, a stand-alone application display, a popup window or dialog box, or an email message.

11. A computer-implemented method, as implemented by one or more computing devices configured with specific executable instructions, comprising:

maintaining application programming interface (API) mapping definitions that map a plurality of proxy APIs to a plurality of backend APIs associated with a backend system;

receiving an API mapping request to create a mapping between a first proxy API and a first backend API, the API mapping request including at least (i) one or more proxy API parameters associated with the first proxy API and (ii) one or more backend API parameters associated with the first backend API;

updating the API mapping definitions such that the API mapping definitions include the mapping between the first proxy API and the first backend API, the updated API mapping definitions configured to cause execution of the first backend API in response to requests to execute the first API proxy;

receiving a proxy API execution request to execute the first proxy API;

in response to the proxy API execution request to execute the first proxy API, determining, based on the updated API mapping definitions, that the first proxy API is mapped to the first backend API; and

transmitting to the backend system a backend API execution request to execute the first backend API on the backend system.

12. The computer-implemented method of claim 11, wherein the one or more proxy API parameters include one or more of a function name associated with the first proxy API, an input parameter associated with the first proxy API, or an output parameter associated with the first proxy API, and the one or more backend API parameters include one or more of a function name associated with the first backend API, an input parameter associated with the first backend API, or an output parameter associated with the first backend API.

13. The computer-implemented method of claim 11, wherein the one or more proxy API parameters specify a proxy output format in which a result of executing the first proxy API is to be provided, and the one or more backend API parameters specify a backend output format in which a result of executing the first backend API on the backend system is to be provided.

14. The computer-implemented method of claim 11, wherein the API mapping request further includes a cache parameter for setting a duration for maintaining a cached result associated with executing at least one of the first proxy API or the first backend API.

15. The computer-implemented method of claim 11, wherein the API mapping request further includes a security parameter for limiting access to at least one of the first proxy API or the first backend API.

16. Non-transitory physical computer storage storing computer-executable instructions, which, when executed by one or more computing devices, configure the one or more computing devices to:

maintain application programming interface (API) mapping definitions that map a plurality of proxy APIs to a plurality of backend APIs associated with a backend system;

receive an API mapping request to create a mapping between a first proxy API and a first backend API, the API mapping request including at least (i) one or more proxy API parameters associated with the first proxy API and (ii) one or more backend API parameters associated with the first backend API;

update the API mapping definitions such that the API mapping definitions include the mapping between the first proxy API and the first backend API, the updated API mapping definitions configured to cause execution of the first backend API in response to requests to execute the first API proxy;

receive a proxy API execution request to execute the first proxy API;

in response to the API execution request to execute the first proxy API, determine, based on the updated API mapping definitions, that the first proxy API is mapped to the first backend API; and

transmit to the backend system a backend API execution request to execute the first backend API on the backend system.

17. The non-transitory physical computer storage of claim 16, wherein the one or more proxy API parameters include one or more of a function name associated with the first proxy API, an input parameter associated with the first proxy API, or an output parameter associated with the first proxy API, and the one or more backend API parameters include one or more of a function name associated with the first backend API, an input parameter associated with the first backend API, or an output parameter associated with the first backend API.

18. The non-transitory physical computer storage of claim 16, wherein the one or more proxy API parameters specify a proxy output format in which a result of executing the first proxy API is to be provided, and the one or more backend API parameters specify a backend output format in which a result of executing the first backend API on the backend system is to be provided.

19. The non-transitory physical computer storage of claim 16, wherein the API mapping request further includes a cache parameter for setting a duration for maintaining a cached result associated with executing at least one of the first proxy API or the first backend API.

20. The non-transitory physical computer storage of claim 16, wherein the API mapping request further includes a security parameter for limiting access to at least one of the first proxy API or the first backend API.