IP Library Granted Patent US 11,275,636
Granted Patent B1
US 11,275,636 · App. 16/918,594 · Granted Mar 15, 2022

Data driven API conversion

Inventor: Thomas R. Kennedy, Jr. (Miami Beach, FL)
Assignee: Vinyl Development LLC
G06F9/547H04L63/083H04L67/02H04L67/2823H04L69/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,275,636
App. No.
16/918,594
Granted
Mar 15, 2022
Kind
B1
Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for a dynamic api, includes receiving a first message in a first format from a client, the first format being specified for the client, the first message including information sufficient to cause a target service to execute an operation. The method includes identifying, using the API message, the target service. The method includes determining based of the target, a second format. The method includes generating a second message in the second format prescribed by the target service using the first message, the second message including information sufficient to cause the target service to execute the operation. The method also includes sending the second message to the target service over the network connector.

Claims (65)

1. A system comprising:

one or more storage devices storing instructions that are operable, when executed by one or more computers, to cause the one or more computers to perform operations comprising:

receiving, from a client device, data specifying a first format for one or more messages receivable from the client device and a response format for one or more response messages for sending to the client device;

receiving a first message in the first format from the client device, the first message including information sufficient to cause a target service to execute an operation;

determining, based on the client device, a type of authentication for validating the first message;

validating the first message in accordance with the type of authentication;

generating a second message in a second format using the first message, the second format being different from the first format, the second message including information sufficient to cause the target service to execute the operation;

sending the second message to the target service; and

sending, to the client device, a response message in the response format.

2. The system of claim 1 , further comprising:

receiving results from the target service in a first return format; and

modifying the results to a second return format, the second return format selected based on the data specifying the response format from the client device.

3. The system of claim 1 , further comprising:

identifying an error code and an error message received from the target service;

generating an error in the response format; and

sending the error message to the client device.

4. The system of claim 1 , further comprising:

identifying at least one error returned from the target service; and

providing the error to the client device in a second error format, the second error format determined based on the response format.

5. The system of claim 1 , further comprising:

authenticating the sending using a first authentication method different from a second authentication method used in the second message.

6. The system of claim 1 , wherein the system is operated by the client device.

7. The system of claim 1 , wherein the target service is a RESTful service.

8. A computer-implemented method comprising:

receiving, from a client device, data specifying a first format for one or more messages receivable from the client device and a response format for one or more response messages for sending to the client device;

receiving a first message in the first format from the client device, the first message including information sufficient to cause a target service to execute an operation;

determining, based on the client device, a type of authentication for validating the first message;

validating the first message in accordance with the type of authentication;

generating a second message in a second format using the first message, the second format being different from the first format, the second message including information sufficient to cause the target service to execute the operation;

sending the second message to the target service; and

sending, to the client device, a response message in the response format.

9. The computer-implemented method of claim 8 , further comprising:

receiving results from the target service in a first return format; and

modifying the results to a second return format, the second return format selected based on the data specifying the response format from the client device.

10. The computer-implemented method of claim 8 , further comprising:

identifying an error code and an error message received from the target service;

generating an error in the response format; and

sending the error message to the client device.

11. The computer-implemented method of claim 8 , further comprising:

identifying at least one error returned from the target service; and

providing the error to the client device in a second error format, the second error format determined based on the response format.

12. The computer-implemented method of claim 8 , further comprising:

authenticating the sending using a first authentication method different from a second authentication method used in the second message.

13. The computer-implemented method of claim 8 , wherein the target service is a RESTful service.

14. A non-transitory computer storage medium encoded with computer program instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

receiving, from a client device, data specifying a first format for one or more messages receivable from the client device and a response format for one or more response messages for sending to the client device;

receiving a first message in the first format from the client device, the first message including information sufficient to cause a target service to execute an operation;

determining, based on the client device, a type of authentication for validating the first message;

validating the first message in accordance with the type of authentication;

generating a second message in a second format using the first message, the second format being different from the first format, the second message including information sufficient to cause the target service to execute the operation;

sending the second message to the target service; and

sending, to the client device, a response message in the response format.

15. The non-transitory computer storage medium of claim 14 , the operations further comprising:

receiving results from the target service in a first return format; and

modifying the results to a second return format, the second return format selected based on the data specifying the response format from the client device.

16. The non-transitory computer storage medium of claim 14 , the operations further comprising:

identifying an error code and an error message received from the target service;

generating an error in the response format; and

sending the error message to the client device.

17. The non-transitory computer storage medium of claim 14 , the operations further comprising:

identifying at least one error returned from the target service; and

providing the error to the client device in a second error format, the second error format determined based on the response format.

18. The non-transitory computer storage medium of claim 14 , the operations further comprising:

authenticating the sending using a first authentication method different from a second authentication method used in the second message.

19. The non-transitory computer storage medium of claim 14 , wherein the target service is a RESTful service.

Assignments (4)
SECURITY INTEREST Recorded Mar 23, 2023
From: JITTERBIT, INC.
To: CRESTLINE DIRECT FINANCE, L.P.
Reel/Frame 063069/0088 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 062941 FRAME: 0640. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 15, 2023
From: VINYL DEVELOPMENT LLC
To: JITTERBIT, INC.
Reel/Frame 063101/0532 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 10, 2023
From: VINYL DEVELOPMENT, LLC
To: JITTERBIT, INC.
Reel/Frame 062941/0640 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 16, 2020
From: KENNEDY, THOMAS R., JR.
To: VINYL DEVELOPMENT LLC
Reel/Frame 054375/0466 →
Continuity (2)
Continuation 16361838 · Mar 22, 2019
Continuation 15654319 · Jul 19, 2017