Overview
This article outlines the high‑level integration models used to support applicant data exchange between an ATS and Radancy CRM.
The model used depends on ATS capabilities, security requirements, and customer needs.
1. Direct ATS Integration
Radancy connects directly to the ATS using native APIs or reporting endpoints.
Typical characteristics:
- ATS‑specific APIs or reporting frameworks (SOAP, REST, XML reports)
- Customer‑provisioned credentials
This is the most common model when the ATS supports direct access.
2. Middleware‑Based Integration
Radancy connects to a middleware platform that normalizes ATS data before passing it to Radancy CRM.
Middleware is typically used when:
- The ATS is not directly supported
- Resume delivery is required in the applicant feed
3. Flat‑File Integration
The ATS sends applicant data to Radancy via scheduled file transfers.
Typical characteristics:
- XML file delivery
- SFTP transport
- Scheduled batch processing
This model is used when:
- APIs are unavailable or restricted
- Middleware is not an option
- The ATS supports export‑based data sharing only
FTP ownership (Radancy‑managed vs customer‑managed) is determined during implementation.
Environments & Testing
Applicant integrations typically involve:
- Non‑Production environments – Configuration, testing, and validation
- Production environments – Live integrations
Environment strategy is confirmed during implementation planning.