IP Library Granted Patent US 10,282,241
Granted Patent B1
US 10,282,241 · App. 15/654,319 · Granted May 7, 2019

Data driven API conversion

Inventor: Thomas R. Kennedy, Jr. (Miami Beach, FL)
Assignee: Vinyl Development LLC
G06F9/547H04L63/083H04L67/02
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 10,282,241
App. No.
15/654,319
Granted
May 7, 2019
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 (79)

1. A system comprising:

a network connector;

a non-transitory computer storage medium 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, for the client device, 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;

identifying, from the first message, the target service by parsing the first message according to the data specifying the first format;

determining, based on the target service that is identified, a second format;

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;

sending the second message to the target service over the network connector; and

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

wherein the one or more computers are configured to:

receive messages in a plurality of different formats and that specify respective corresponding target services, and

generate, for each received message, a corresponding message based on a format corresponding to a respective target service, and

wherein the messages include at least two messages having different formats and identifying the same corresponding target service.

2. The system of claim 1 , further comprising:

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

generating results in a second return format, the second return format selected based on a sender of the first message.

3. The system of claim 2 , further comprising:

identifying an error code and an error message within the results;

generating an error in a format specified by the sender; and

sending the error message to the sender.

4. The system of claim 1 , further comprising:

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

providing the error to a sender of the first message in a second error format, the second error format determined based on the sender.

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 receives request from a sender over a network.

7. The system of claim 1 , wherein the system is operated by a sender of the first message.

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

9. A computer-implemented method comprising:

receiving, by a computer system and from a client device, data specifying, for the client device, 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, by the computer system, 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;

identifying, from the first message, the target service by parsing the first message according to the data specifying the first format;

determining, based on the target service that is identified, a second format;

generating, by the computer system, 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;

sending the second message to the target service over a network connector; and

sending, to the client device, a response in the response format;

wherein the computer system is configured to:

receive messages in a plurality of different formats and that specify respective corresponding target services, and

generate, for each received message, a corresponding message based on a format corresponding to a respective target service, and

wherein the messages include at least two messages having different formats and identifying the same corresponding target service.

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

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

generating results in a second return format, the second return format selected based on a sender of the first message.

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

identifying an error code and an error message within the results;

generating an error in a format specified by the sender; and

sending the error message to the sender.

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

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

providing the error to a sender of the first message in a second error format, the second error format determined based on the sender of the first message.

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

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

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

15. 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, for the client device, 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;

identifying, from the first message, the target service by parsing the first message according to the data specifying the first format;

determining, based on the target service that is identified, a second format;

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;

sending the second message to the target service over the network connector; and

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

wherein the one or more computers are configured to:

receive messages in a plurality of different formats and that specify respective corresponding target services, and

generate, for each received message, a corresponding message based on a format corresponding to a respective target service, and

wherein the messages include at least two messages having different formats and identifying the same corresponding target service.

16. The non-transitory computer storage medium of claim 15 , further comprising:

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

generating results in a second return format, the second return format selected based on a sender of the first message.

17. The non-transitory computer storage medium of claim 16 , further comprising:

identifying an error code and an error message within the results;

generating an error in a format specified by the sender; and

sending the error message to the sender.

18. The non-transitory computer storage medium of claim 16 , further comprising:

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

providing the error to the sender in a second error format, the second error format determined based on the sender.

19. The non-transitory computer storage medium of claim 15 , further comprising:

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

20. The non-transitory computer storage medium of claim 15 , 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 Jul 19, 2017
From: KENNEDY, THOMAS R.
To: VINYL DEVELOPMENT LLC
Reel/Frame 043047/0226 →