Purpose
This article documents the Radancy Standard Applicant Fields Model used for Flat‑File (SFTP) applicant integrations.
It is intended for technical customer contacts who manage or support applicant data delivery via scheduled flat‑file transfers. This document defines the supported applicant and application fields, their requirement levels, and formatting expectations.
Important:
The table below is the authoritative source for field definitions. Field names, data types, and requirement levels must not be altered outside of Radancy‑approved integration changes.
How to Use This Reference
Use this article to:
- Validate applicant and application data included in flat‑file (SFTP) deliveries
- Confirm which fields are Required, Recommended, or Optional
- Understand formatting expectations for applicant integrations that do not use APIs
This article does not provide:
- ATS‑specific field mapping instructions
- Configuration steps for SFTP setup
- Troubleshooting guidance
Those details are addressed during implementation or in ATS‑specific documentation.
Field Requirement Definitions
Fields in the table are classified as follows:
- Required – Must be present for the integration to function correctly
- Recommended – Strongly encouraged to support matching, search, and reporting
- Optional – Not required, but supported when available
| Field Name | Description | Required | Editable |
| emailAddress | String. Email address of candidate | Required | No |
| importCreationDate | DateTime | Optional | |
| importUpdateDate | DateTime | Optional | |
| atsProfileUpdateDate | DateTime | Required | |
| applicantId | String. The unique id of candidate from ATS | Required | No |
| startDate | Nullable DateTime. Applicant’s start date (Hired state) | Required | |
| firstName | String | Recommended | |
| Address | Concrete object type | ||
| country | String (Full name or ISO 2-Digit Alpha Country Code. If ISO 3-Digit Alpha Country Code, not able to import to CRM) | Recommended | |
| state | String (Full name) | Recommended | |
| stateCode | String (2-Digit state code. State or StateCode, provide either of them) | Recommended | |
| city | String | Recommended | |
| address | String | Optional | |
| address2 | String | Optional | |
| zipcode | String | Recommended | |
| Phone Number(s) | Array Type | ||
| Type | Integer. Enum stands for phone type (1: HomePhone, 2: MobilePhone, 3: OfficePhone) | Recommended | |
| Value | String. Phone number | Recommended | |
| Education(s) | Array Type | ||
| schoolName | String | Recommended | |
| major | String | Recommended | |
| degreeObtained | String | Recommended | |
| startMonth | Nullable integer | Optional | |
| startYear | Nullable integer | Optional | |
| endMonth | Nullable integer | Optional | |
| endYear | Nullable integer | Recommended | |
| IsCurrent | Boolean. Is currently working or studying here? | Recommended | |
| Work Experience(s) | Array Type | ||
| companyName | String | Recommended | |
| title | String | Recommended | |
| workDescription | String | Recommended | |
| startMonth | Nullable integer | Recommended | |
| startYear | Nullable integer | Recommended | |
| endMonth | Nullable integer | Recommended | |
| endYear | Nullable integer | Recommended | |
| IsCurrent | Boolean. Is currently working or studying here? | Recommended | |
| Tags | Array Type | ||
| tag | String. Candidate tag set in ATS profile. Include Tag ID attribute if available. | Optional | |
| Application(s) | Array Type | ||
| applicationId | String. Job application id from ATS | Required | No |
| reqId | String. Job requisition id | Required | |
| title | String. Job title | Required | |
| applicantId | String. The unique id of candidate from ATS | Required | |
| importCreationDate | DateTime | Optional | |
| importUpdateDate | DateTime | Optional | |
| atsUpdateDate | DateTime. Job application update time from ATS | Required | |
| status | Application Object type. Saves the current status of this application | ||
| mainStatus | String. Main status of current application | Required | |
| subStatus | String. Sub status of current application | Required | |
| updated | DateTime. Job application update time from ATS | Required | |
| Profile | Application Object type. Properties described below in "Profile" cells | ||
| applicationDate | Nullable DateTime | Optional | |
| hireDate | Nullable DateTime | Optional | |
| startDate | Nullable DateTime | Optional | |
| ethnicity | String | Optional | |
| gender | String | Optional | |
| atsSource | String | Optional | |
| jobInformation | Application Object type. Saves job information of this application. | ||
| businessUnit | String | Optional | |
| department | String | Optional | |
| function | String | Optional | |
| positionLevel | String | Optional | |
| jobCategory | String | Optional | |
| jobCity | String | Optional | |
| jobState | String | Optional | |
| jobPostalCode | String | Optional | |
| jobRegion | String | Optional | |
| jobCountry | String | Optional | |
| statusHistory | Application Object type. List of all previous Status types. | ||
| mainStatus | String | Recommended | |
| subStatus | String | Recommended | |
| updated | DateTime | Recommended |
The following formatting standards apply to flat‑file integrations:
- DateTime values
- Format:
YYYY-MM-DDThh:mm:ss - Example:
2021-02-20T04:05:27
- Format:
- Phone Numbers
- Multiple formats are supported
- Validation occurs during UAT
Failure to meet formatting requirements may result in data rejection or incomplete processing.
Important Notes
- Not all ATS platforms can supply every field listed in the model
- Required fields must always be present for integration stability
- Recommended fields significantly improve downstream functionality
- Any changes to ATS workflows, statuses, or exports should be communicated to Radancy prior to implementation