arya ats and crm api integration overview...arya ats and crm api integration overview leoforce...

Arya ATS and CRM API Integration Overview

Leoforce Proprietary Jan-2019 1

I. Arya API Integration Overview for ATS & CRM Databases

A. Arya AI Candidate Sourcing Overview The Arya Artificial Intelligence-based (AI) candidate sourcing recruiting solution for staffing and talent acquisition professionals has been designed as an open platform designed to integrate with each of our client’s Applicant Tracking Systems (ATS), Candidate Relationship Management (CRM), and/or Recruitment Marketing systems through the use of standard APIs (Application Programming Interface, a methodology to enable secure communications between two computer systems). A high-level overview of the process that Arya utilizes to source qualified candidates for open jobs includes:

1) Arya analyzes and evaluates information in the Job Requisition (Job Description, Job Posting, Job Order, etc.) using our proprietary intelligent parsing, natural language processing, predictive textual analytics, deep learning, neural networks, and machine learning algorithms which have been refined from sourcing tens of millions of candidates for hundreds of thousands of job activations to create a sophisticated Boolean search string to identify, rate, rank, and present the most qualified candidates.

2) Depending on the Arya configuration by the client and specific instructions from the

Recruiter (Arya user), Arya sources qualified candidates from:

a. Internal candidate databases (i.e. ATS or CRM applicants and candidates); b. Leading Industry Job Boards using client subscription credentials; and/or c. Arya’s Social Index of several hundred million passive candidates from publicly

available professional profiles on dozens of global social platforms.

3) The Recruiter provides Arya with additional critical feedback on candidates (via Shortlist and Ignore) which reactivates the machine learning algorithms and neural network processing to refine the search criteria to optimize the slate of candidates presented by Arya.



The following diagram summarizes the typical integration scenario when utilizing APIs to integrate a client’s ATS or CRM system with Arya.

B. Arya API Integration Scenarios There are several approaches to integrate Arya with client ATS and CRM systems, including:

1) Arya can be configured to consume APIs published by our ATS and CRM solution partners (typical scenario).

2) Arya can be configured to integrate with APIs developed to integrate with proprietary

client candidate databases.

3) Arya ATS and CRM solution partners can consume the Arya Open APIs.

1. Arya exchanges API

AuthenticationCredentials with ATS

2. Arya issues API to GET

a list of new Jobs (status, date range, etc.)


Job Requisition Details for new Jobs

2. Arya User PUSHes new

Shortlisted Candidate(s) back to ATS or CRM


new Candidates from to synch with Arya




list of Open / Active Jobs


Job Requisition Details for Jobs


list of relevantCandidates

Startup On-GoingInitiated byArya User


Candidate metadata and resume/CV

3. Arya POSTs status

updates to Internal ATS or CRM candidates





C. Typical Arya API Calls to ATS / CRM Databases Once secure API authentication has been established between Arya and the third-party ATS or CRM partner, the following includes a list of typical API calls to integrate Arya with client ATS and CRM databases.

1) GET Jobs (list of jobs by date range, status, etc.)

2) GET Job (by Job ID)

3) GET Candidates (by client-provided criteria such as last activity date)

4) GET Candidate (by Candidate ID)

5) GET Resume (by Candidate ID, or respective alternatives)

6) POST Candidate (to ATS or CRM, typically “Shortlisted” Candidates)

7) POST Resume (to ATS or CRM)

8) PUT Candidate (Status Update information for ATS or CRM, i.e. connect internal shortlisted candidates to a specific job requisition)

D. Arya Integration Data Fields Illustration Arya Job Data Requirements: Leoforce is interested in importing all pertinent information relative to specific job requirements, experience, and educational and training credentials required. At a minimum, we require:

Client Name (RPO and Staffing firms only) Job ID (Requisition Number) Job Requirements Job Status Job Title

Location (City) Location (Country) Location (State) Location (Zip or Postal Code) Recruiter ID or Recruiter Name

Very important in matching prospective candidates to a job requisition includes:

Experience (Minimum) Experience (Maximum) Location Distance (5, 10, 20, 30, 40, 50, 75, 100 miles; Auto Expand)



Nice to Have in matching prospective candidates to a job requisition includes:

Certification Requirements Education Requirements (degrees, disciplines) Industry Job Openings (quantity) Job Requirements (Must Have)

Job Requirements (Nice to Have) Job Skills Resume Attachment (Gold Star candidate(s) via standard document format)

Arya Candidate Data Requirements: Leoforce is interested in importing and indexing all the information that has been captured on a prospective Candidate, including resume and CV documents. At a minimum, we require:

Candidate Name Candidate Location (City) Candidate Location (Country) Candidate Location (State) Candidate Location (Zip or Postal Code) Current Employer Current Position Title Skills

Very important in matching prospective candidates to a job requisition includes:

Current Position Start Date Current Position Role / Accomplishments Summary

Previous Employer(s) Name Previous Position(s) Title Previous Position(s) Start Date Previous Position(s) End Date Previous Position(s) Role / Accomplishments Summary

Education Credentials (degrees) Education Credentials Award Date Education Institution Industry and Skills Certifications Contact Information (if available) Date & time stamp of metadata (if available)

Nice to Have in matching prospective candidates to a job requisition includes:

Summary of Accomplishments Relevant Research and Publications Resume or CV document

Traditionally, much of this information is text-based and not captured in specific fields (i.e. available in the resume or CV). Arya typically Push(s) all relevant Candidate profile data available for Candidates that have been Sourced and Shortlisted for each Job (dependent on availability of corresponding fields in client’s ATS or CRM database).



II. ATS Integration Configuration Process Overview 1.      SAP provides a SOAP Web Service API integration option to integrate with 3rd party

applications.   2.      The SAP SOAP API specifications are published at the following links:  

https://help.sap.com/doc/74597e67f54d4f448252bad4c2b601c9/1811/en-US/SF_HCM_OData_API_REF_en.pdf

https://help.sap.com/doc/0bd2f6fea0154ac6aacd44f1cacbfc71/1811/en-US/SF_HCM_SFAPI_DEV.pdf   3.      SAP provides the following guidelines to initiate the API integration configuration between

Arya and your SAP SuccessFactors database (from SAP SuccessFactors HCM Suite SFAPI:

Developer Guide, section 4.1 SFAPI Setup):  

Enabling SFAPI In order to use the SFAPI, SuccessFactors must enable the API for your company instance. Please contact your SuccessFactors support representative details to enable the SFAPI for your instance.

API Login Permission Each user of the API must have API Login Permission. An administrator of your SuccessFactors system can grant this permission. The permission setting in the UI is [Symbol] Manage Users [Symbol] API Login Permission. Setting this permission depends on which permission system you are using in your SuccessFactors instance. Below are instructions for each permission system.

Granting API Login Permission in the Traditional (aka User-Based) Permission System API Login Permission is granted in the Admin Tools [Symbol] Manage Users [Symbol] Manage API Login Permission link. This link is highlighted in the following page.

Granting API Login Permission in the Role Based Permission System API Login Permission in the Role Based Permission system is listed under the General User Permission category in the Permission settings page.

5.     Additional information to support the integration process includes:

a. Please provide the approximate number of Job Requisitions to be initially Imported into Arya (to assist with our QA validation process).

b. Please identify which SAP SuccessFactors Job Status(s) or other relevant criteria to be used for importing and activating Jobs in Arya.

https://help.sap.com/doc/74597e67f54d4f448252bad4c2b601c9/1811/en-US/SF_HCM_OData_API_REF_en.pdf

https://help.sap.com/doc/0bd2f6fea0154ac6aacd44f1cacbfc71/1811/en-US/SF_HCM_SFAPI_DEV.pdf



c. Please provide Leoforce with your approximate number of Candidates to be initially Imported into Arya for sourcing.

d. Please identify which SAP SuccessFactors Candidate Status(s) and/or Dates to identify for importing and indexing in Arya for sourcing (and/or any additional attributes to filter the initial Candidate import process).

e. Please provide your SAP SuccessFactors Career Site URL.

f. Please note how frequently you would prefer Arya to resynch Job Requisition information from your SAP SuccessFactors database?

g. Please note how frequently you would prefer Arya to resynch Candidate information from SAP SuccessFactors database?

5.       SAP SuccessFactors API Call Thresholds will need to be validated with the client SAP

Administrator.

III. Key API Integration Milestones 1. Arya Subscription Agreement Executed ........................................................................... Client 2. Client Kick-off Call .................................................................... Client / Leoforce Client Success 3. API Integration Planning Call ...................... Client / ATS Partner (new API Integration) / Leoforce 4. Generate API Authentication Credentials .....................................Client or ATS / CRM Partner 5. Test and Validate API Authentication ......................................................................... Leoforce 6. Export CANDIDATEs for Sourcing .................................................................... Client / Leoforce 7. Import CANDIDATEs into Arya .................................................................................... Leoforce 8. Index CANDIDATEs for Internal Sourcing .................................................................... Leoforce 9. Configure GET (New) JOBs .......................................................................................... Leoforce 10. Configure GET JOB (Details) ....................................................................................... Leoforce 11. Configure GET (New) CANDIDATEs ............................................................................. Leoforce 12. Configure GET CANDIDATE (Resume or CV) ............................................................... Leoforce 13. Configure PUSH CANDIDATE (Shortlist) ..................................................................... Leoforce 14. Quality Assurance Validation ...................................................................................... Leoforce 15. Client Success API Integration Validation.................................................................... Leoforce 16. Client API Integration Review and Validation .................................................................. Client 17. Production API Implementation ................................................................................. Leoforce Typical Arya API Integration implementation timeline is three (3) to six (6) weeks after Leoforce is able to validate the client ATS or CRM API credentials.

arya ats and crm api integration overview...arya ats and crm api integration overview leoforce...

Documents