Unified Integration Pattern Protocol for Centralized Handling of Data Feeds

1. A method for implementing a unified integration pattern (UIP) protocol for file transfers between distinct client systems, comprising: receiving, by a computer system from a sending client system, a first authentication Application Program Interface (API) message and a data file transfer request each for a data transfer event, wherein the sending client system is in a network of distinct client systems and the first authentication API message is in accordance with the UIP protocol; authenticating, by the computer system, the sending client system based on the first authentication API message and the data file transfer request; uploading, by the computer system, in response to authenticating the sending client system based on the first authentication API message, a first data file from the sending client system to the computer system; receiving, by the computer system from the sending client system, a notification API message indicating that initiating the upload of the first data file to the computer system is complete, wherein the notification API message is in accordance with the UIP protocol; sending, by the computer system, to a receiving client system, a notification that the first data file is ready to be transmitted; receiving, by the computer system, a second authentication API message from the receiving client system in response to sending the notification that the first data file is ready to be transmitted, wherein the second API message is in accordance with the UIP protocol; authenticating, by the computer system, the receiving client system based on the second authentication API message; sending, by the computer system to the receiving client system via the UIP protocol, the first data file for downloading by the receiving client system, in response to authenticating the receiving client system based on the second authentication API message; receiving, by the computer system, from the receiving client system, a second notification API message indicating that downloading the first data file has been completed, wherein the second notification message is in accordance with the UIP protocol; receiving, by the computer system, from the receiving client system, information regarding a status of downloading the first data file in a notification message, in response to sending the first data file using the UIP protocol, wherein the notification message is in accordance with the UIP protocol; implementing, by the computer system, responsive to the notification message indicating an error related to downloading the first data file, a function based on a set of predetermined error handling rules; sending, by the computer system via the UIP protocol to the sending client system, the status API message including the information, in response to the sending client system using the UIP protocol; receiving, by the computer system from the sending client system, a third authentication API message in accordance with the UIP protocol; authenticating, by the computer system, the sending client system based on the third authentication API message; receiving, by the computer system from the sending client system, a status inquiry API message in accordance with the UIP protocol in response to authenticating the sending client system based on the second authentication API message; and sending, by the computer system to the sending client system, a status notification message in response to receiving the status inquiry API message.

2. The method of claim 1, further comprising: receiving, by the computer system, an initial authentication API message from the sending client system to be registered with the computer system, wherein the initial authentication API message is in accordance with the UIP protocol; and registering, by the computer system, the sending client system as an authorized user.

3. The method of claim 1, wherein the network of distinct client systems is a human resource management network, the sending client system is an insurance system, and the receiving client system is a data integration system.

4. The method of claim 1, wherein sending, by the computer system, the first data file to a receiving client system in the network of distinct client systems comprises sending the first data file via Secure File Transfer Protocol (SFTP) to the receiving client system.

5. The method of claim 1, wherein the UIP protocol is repeated for multiple client systems of the network of distinct client systems, thereby generating data regarding real-time data transfer events within the network of distinct client systems for use by an error handling module in determining a failure point of one or more of the real-time data transfer events.

6. A system comprising: a processor, a computer readable memory, one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable to: perform an unified integration pattern (UIP) protocol for a first data file transfer event by: receiving a first authentication Application Program Interface (API) message and a data file transfer request from a sending client system in a network of distinct client systems, wherein the first authentication API message is in accordance with the UIP protocol; authenticating the sending client system based on the first authentication API message; initiating transfer of a first data file to a computer system from the sending client system in response to authenticating the sending client system based on the first authentication API message; receiving a notification API message from the sending client system indicating that initiating the transfer of the first data file to the computer system is complete, wherein the notification API message is in accordance with the UIP protocol; sending, to a receiving client system, a notification that the first data file is ready to be transmitted; receiving a second authentication API message from the receiving client system in response to the notification that the first data file is ready to be transmitted, wherein the second authentication API message is in accordance with the UIP protocol; authenticating the receiving client system based on the second authentication API message; sending the first data file to the receiving client system by the UIP protocol, for downloading by the receiving client system in response to authenticating the receiving client system based on the second authentication API message; receiving a second notification API message from the receiving client system indicating that downloading the first data file has been completed, wherein the second notification API message is in accordance with the UIP protocol; receiving, from the receiving client system, information regarding a status of downloading the first data file in a notification message, in response to sending the first data file using the UIP protocol, wherein the notification message is in accordance with the UIP protocol; implementing a function based on a set of predetermined error handling rules, responsive to the notification message indicating an error related to downloading the first data file; sending a notification message to the sending client system via the UIP protocol, in response to sending the first data file using the UIP protocol, the notification message including the information and indicating that the first data file transfer event has been completed; receiving a third authentication API message from the sending client system, wherein the third authentication API message is in accordance with the UIP protocol; authenticating the sending client system based on the third authentication API message; receiving a status inquiry API message from the sending client system in response to authenticating the sending client system based on the third authentication API message, wherein the status inquiry API message is in accordance with the UIP protocol; and sending a status notification to the sending client system in response to receiving the status inquiry API message.

7. The system of claim 6, wherein performing the UIP protocol for the first data file transfer event further comprises: receiving an initial authentication API message from the sending client system to be registered with the computer system, wherein the initial authentication API message is in accordance with the UIP protocol; and registering the sending client system as an authorized user.

8. The system of claim 7, wherein performing the UIP protocol for the first data file transfer event further comprises: receiving a fourth authentication API message from the receiving client system to be registered with the computer system, wherein the fourth authentication API message is in accordance with the UIP protocol; and registering the receiving client system as an authorized user.

9. The system of claim 6, wherein the program instructions are further executable to: repeat the UIP protocol for a second data transfer event between other sending client systems and other receiving client systems in the network of distinct client systems for each of a plurality of additional real-time data transfer events, wherein the UIP protocol generates data regarding a status of the first data file transfer event in real-time and additional real-time data transfer events.

10. The system of claim 9, wherein the UIP protocol generates error data regarding the first data file transfer event and the additional real-time data transfer events within the network of distinct client systems for use by an error handling module in determining a failure point of one or more of the first data file transfer event and the additional real-time data transfer events within the network of distinct client systems.

11. The system of claim 6, wherein the network of distinct client systems is a cloud-based network platform providing services to consumers over a cloud network.

12. A non-transitory computer readable storage media having one or more instructions executable by one or more processors to: perform a unified integration pattern (UIP) protocol for a first data file transfer event by: receiving a first authentication Application Program Interface (API) message and a data file transfer request from a sending client system in a network of distinct client systems, wherein the first authentication API message is in accordance with the UIP protocol; authenticating the sending client system based on the first authentication API message; initiating transfer of a first data file to a computer system from the sending client system in response to authenticating the sending client system based on the first authentication API message; receiving a notification API message from the sending client system indicating that initiating the transfer of the first data file to the computer system is complete, wherein the notification API message is in accordance with the UIP protocol; sending, to a receiving client system, a notification that the first data file is ready to be transmitted; receiving a second authentication API message from the receiving client system in response to the notification that the first data file is ready to be transmitted, wherein the second authentication API message is in accordance with the UIP protocol; authenticating the receiving client system based on the second authentication API message; sending the first data file to the receiving client system by the UIP protocol, for downloading by the receiving client system in response to authenticating the receiving client system based on the second authentication API message; receiving a second notification API message from the receiving client system indicating that downloading the first data file has been completed, wherein the second notification API message is in accordance with the UIP protocol; receiving, from the receiving client system, information regarding a status of downloading the first data file in a notification message, in response to sending the first data file using the UIP protocol, wherein the notification message is in accordance with the UIP protocol; implementing a function based on a set of predetermined error handling rules, responsive to the notification message indicating an error related to downloading the first data file; sending a notification message to the sending client system via the UIP protocol, in response to sending the first data file using the UIP protocol, the notification message including the information and indicating that the first data file transfer event has been completed; receiving a third authentication API message from the sending client system, wherein the third authentication API message is in accordance with the UIP protocol; authenticating the sending client system based on the third authentication API message; receiving a status inquiry API message from the sending client system in response to authenticating the sending client system based on the third authentication API message, wherein the status inquiry API message is in accordance with the UIP protocol; and sending a status notification to the sending client system in response to receiving the status inquiry API message.

13. The non-transitory computer readable storage media of claim 12, wherein performing the UIP protocol for the first data file transfer event further comprises: receiving an initial authentication API message from the sending client system to be registered with the computer system, wherein the initial authentication API message is in accordance with the UIP protocol; and registering the sending client system as an authorized user.

14. The non-transitory computer readable storage media of claim 13, wherein performing the UIP protocol for the first data file transfer event further comprises: receiving a fourth authentication API message from the receiving client system to be registered with the computer system, wherein the fourth authentication API message is in accordance with the UIP protocol; and registering the receiving client system as an authorized user.

15. The non-transitory computer readable storage media of claim 12, wherein the one or more instructions are further executable to: repeat the UIP protocol for a second data transfer event between other sending client systems and other receiving client systems in the network of distinct client systems for each of a plurality of additional real-time data transfer events, wherein the UIP protocol generates data regarding a status of the first data file transfer event in real-time and additional real-time data transfer events.

16. The non-transitory computer readable storage media of claim 15, wherein the UIP protocol generates error data regarding the first data file transfer event and the additional real-time data transfer events within the network of distinct client systems for use by an error handling module in determining a failure point of one or more of the first data file transfer event and the additional real-time data transfer events within the network of distinct client systems.

17. The non-transitory computer readable storage media of claim 12, wherein the network of distinct client systems is a cloud-based network platform providing services to consumers over a cloud network.