Certifying the API
Once you’ve developed the utility to push the decided data scope to SmashFly, you can begin the testing process.
Before testing, you must provide the following to your SmashFly Technical Services Consultant:
- A sample of your Jobs XML with information about how the nodes map to fields (both standard and custom).
- Email addresses to which job import notifications should be sent.
The SmashFly Technical Services Consultant will perform the following steps:
- Map the nodes to fields in the back-end Staging administration system. Note that if the mapping needs to change after initial submission of information, your SmashFly Technical Services Consultant must update this mapping in order for information submitted to land as expected.
- Validate that the data in the XML file looks correct and will map correctly into the fields designated. If changes are needed, the SmashFly Technical Services Consultant will communicate them at this time.
- Configure email addresses to receive the job import notification email in the Staging environment.
- Create a test Username and Password in the Staging Environment. SmashFly will need to provide these to you to allow connectivity testing and execution through the API.
- Once the Username and Password are provided to you, push Job data to the Staging Environment at the Staging Service URL.
- Once you have successfully implemented and tested your solution within the Staging Environment, please contact your SmashFly Technical Services Consultant to provide a final version of the job XML. The SmashFly Technical Services Consultant will review the file and any additional information you provided for final validation and certification.
Recommended Data Validation
SmashFly recommends that for the first few iterations of testing in Staging, you test connectivity by sending a manually created job to the Staging environment. Once connectivity is confirmed, send a few separate calls containing multiple jobs with real job data across to SmashFly to test the Add, Update, and Delete actions.
To review the data in the system, log into the Staging Environment at https://recruitstagep.smashfly.com using your API credentials. Review all data for accuracy, paying careful attention to the following, which are critically important:
- Job ID. Confirm that the ATS Job ID is displaying as expected in the Job ID field. The Job ID is used downstream for Advanced Pipeline Metrics (when these are in scope) and is leveraged for job board postings.
- Apply URL. Confirm that the Job Apply URL (ApplyURL) lands in the correct spot. Note that typically, you need to submit only the URL for the job description page (without any additional parameters, like source) to SmashFly. Ensure that when you navigate to the listed Apply URL, you successfully land on the expected job.
- Job Location. Confirm that Job Country, State/Province, City, and ZIP Code populate as expected, ensuring particularly that any lookup options are selected as expected (for example, in Country and State).
- Select Fields. Confirm that any “Select” fields (both standard and custom)— where a list of values is available for selection — can be selected correctly through the API. For the correct value to be selected, the CODE value must be submitted.
- Job Description Formatting. The Job Description field accepts full HTML formatting. View this job formatting in the SmashFly system (and if possible and in scope, on the Career Marketing Site). Adjust the formatting as needed. Note that SmashFly cannot modify or transform the Job Description systematically as it comes into the system, so any ATS formatting errors or issues (such as MSO invisible code or extraneous paragraph tags) must be rectified in the source system before the description is submitted to SmashFly.
- Intellipost Rules. Intellipost rules can transform most fielded job data as a job is added or updated to the system. Intellipost rules are typically used to populate the following fields: Company, Contact First Name, Contact Last Name, Contact Email Address, Standard Job Type, and SmashFly Job Category/Code. Make sure that any other necessary data transformation is taking place as expected for job-level data (Posting Fields Mapping, Contact Database Mappings, and Header/Footer Mappings). Evaluate whether additional rules are needed to support the job marketing use case both at the job level and at the board-level (for example, Board Posting Rules, Field Mappings, and so on).
This is the Staging Service URL:
Your SmashFly Technical Services Consultant will provide you with the production URL after final validation of your Job API implementation in the Staging environment.