Data from an internal system to Rival Recruit

Rival Recruit employs a data import model whereby the customer’s internal system(s) may serve as the source for key data elements necessary to create a job record. By using our XML import interface, an organization can keep certain support data up to date without the need for manual administration by a user, ultimately saving time and resources.

Using a set of Rival Recruit-defined schema, XML data files are constructed by a customer’s data administration or information technology group and then posted to a Rival Recruit server via a simple HTTPS form post action (SSL 128 bit encrypted). Our server processes the file and updates key data tables in real-time ensuring that the data available to your users is accurate and up to date.

For data to get from your internal system to Rival Recruit, the following steps must occur. If you are finding an issue with the data on Rival Recruit and you are sure that the data originates in your internal system, the best way to troubleshoot is to start at the top of this list and work your way downwards ensuring that each step has occurred as it should. That is why troubleshooting the process one step at a time is so critical. The issue could be on either side of the integration.

1. Customer process extracts data from internal system and converts data to XML format acceptable to Rival Recruit’s interface.
2. Customer process posts XML data file to Rival Recruit server.
3. Rival Recruit server attempts to read file. If it cannot read the file, it provides error response in the HTTP post response header.
4. If the Rival Recruit process can read the file, the data is imported into a staging area where additional data format validation is performed. Data that meets the validation requirements is imported directly into the Rival Recruit database where a user can view it.