Recruiter System Connect - Developer FAQs

Please reference RSC developer documentation

Reach out to LinkedIn Business Development to fill out the Onboarding Request Form and follow steps in the RSC developer documentation.

New Talent Solutions integrations like Recruiter System Connect are built on the Middleware Platform, which means you should manage job applications via the /atsApplications and /atsCandidates endpoint instead of /simpleJobApplications. If you’ve previously integrated with LinkedIn Referrals, you’ll need to switch to using the Middleware Platform for submitting job applications.

No. The minimum product and technical requirements for RSC are indicated in this document and partners may not elect to enable a subset.

We require all historical candidate, applications, and jobs records to ensure LinkedIn Recruiter is as valuable as possible for your customers [i.e. the “Rediscovered Candidates” Spotlight, ‘In-ATS Indicator’]

Many customers will not need to do so if their privacy policies allows them to share candidate data to their third party partners. However, customers will need to consult their own legal teams regarding this prior to activating RSC. Some partners include a disclaimer in the onboarding widget that requires the customer to authorize the sharing of ATS data with LinkedIn.

Customers will be able to turn on all their middleware integrations via a widget in the ATS and in their Recruiter dashboard. See technical docs

• If the customer wants to delete candidate records: Partner should call Delete End Points highlighted in developer docs for Sync Candidates, Notes, Interview Notes, Applications
• If the customer wants to delete all their data for an ATS (including Jobs): Partner should contact ltsatsintegrations@linkedin.com
• Note: Once delete is processed, all copies of data will be deleted within 30 days

Customers must email the Partner and LinkedIn support notifying us they would like to deactivate RSC. Customer can contact LinkedIn support at ltsatsintegrations@linkedin.com

Rcorp (Recruiter Corporate), RPS (Recruiter Professional Services), and Recruiter SMB

The ATS partner can confirm the duplication was handled in the ATS when LI passes back the PersonURN (Member ID) to the ATS Partner

LinkedIn members that don't have their privacy settings set to share their profile with third parties will not have One-Click Export functionality enabled.

Customer can create a standard "dummy req" field in the drop down that Recruiter will be able to export the candidate to if they do not want to associate the candidate with a Job Req. ATS can then conduct any matching required on their end. However, customers will need to consult their legal team to determine if they can export data unassociated with a requisition.

Yes it will show all open jobs that the user has permissions to see based on Security Groups. If a Partner has not enabled Security Groups, all open jobs will be seen by all users. Customers can search for jobs based on type head

Call volume for One-Click Export is 300 calls per Recruiter seat per month. LinkedIn reserves the right to change rate limits including to prevent abuse and protect privacy and security.

ATS will validate this push event against the signature in the request, outlined in our documentation.

This is an expected behavior, when companyJobCode exist, it takes precedence over externalJobPostingId

LI will post jobs based on the language that the customer posts in. If the job requires multiple languages, the customer should have separate listings for each language.

The preferred integration is to send in real-time

Jobs will default to 180 days if there is no expiration date passed in.

For jobs with multiple locations, the current solution is to post one requisition per location. Or, send only the primary location if that designation exists. For jobs with no location (e.g. virtual jobs), you may either:

1. Not send these jobs, or

2. Default to a specific location (for example, headquarter). Jobs will not be posted without a location

No, the way the middleware platform is architected, it needs to be through the Simple Job Posting API.

Yes, LinkedIn integrations are set up at the contract level, so customers can have separate integrations for any of their contracts. Recruiter users can switch between contracts, and each contract can be associated with one or more integrations. Partners must be able to support multiple contracts for the same customer.

There is an “Send InMail” button in the profile widget that allows sending InMails.

It sends a notification to the ATS user in LinkedIn Recruiter when there are profile updates for the relevant candidate.

If a candidate deletes their LinkedIn account, they can reactivate it within 21 days. After 21 days, we purge the deleted accounts and populate that information within the Closed Candidates Endpoint. Our ATS partners must query this endpoint periodically (at least once in 30 days) and purge the accounts (that appear within this endpoint) from their records.

Yes, it's an all-or-nothing integration (with the exception of the feature that enables the sending of Interview Notes and Feedback to LinkedIn Recruiter, which is optional) ; however partners can test and certify each module along the way prior to launch.

The requirements are laid out in the developer and required fields documentation.

First name and last name are used as part of our matching algorithm, though the fields are optional. The preference would be to split firstName and lastName if you have it

• Email is required when available.
• The only instance when email address may be omitted for a Candidate is via One-Click Export as documented here.

The throttling is based on the number of API calls being made. We don't have any maximum limits of how much data can be synced by customers.

The Sync API will consider any data after the initial push as an update. As long as you are sending the correct fields and values against it, there should be no problem.

This varies across our ATS partners, however we generally see this reflected within a few minutes. Ideally this should be as real-time as possible.

Yes, the button should show up if there was a network error. Once the request is sent, the button changes to Notify Partner, after this you should be able to call /atsIntegrations API.

People are matched on the basis of email first and then phone number, subject to the relevant member’s privacy settings. If the matching made is incorrect or cannot be found, LinkedIn allows the Customer to manually match in the Profile Widget. Refer to this API. This updates the 'manualMatchedMember' attribute for synced candidates. It is advised that if the value for the manualMatchedMember field is present then ATS should always use that instead of the values present in the 'matchedMembers' attribute.

The jobs are sent in a sequence and also returned back in a sequence. So you would be keeping track of the sequence and able to match it accordingly.

No.

The minimum character length is to ensure this is a genuine job and not spam. We accept only quality jobs so that is why we have the restriction. If the description is within 10K characters, this should be fine.

Within the widget there is a callback function parameter which on link / unlink allows your system to add or update the appropriate person URN to update and store. The person URN connects the candidate to the job post and all other information related to the candidate including notes, job application status, etc.

Use in.parse() to reload the widget on a single page application.

The Linkedin LTS Partner Operations (PO) team proactively renews contracts. This is a monthly activity and we renew your contract once its near expiry. This gives a seamless LinkedIn RSC experience without the need to raise a ticket for contract renewal.

It is recommended to test the InMail functionality for RSC Integrations by sending InMails to your first degree connections. One can send unlimited inMails because there is no restriction to it. To be able to test this feature, the users should be connected to the developers of our team.

Through ACL, we control the visibility of any jobs to only user(s). ACLs consist of two parts - atsEntityAcls for groups and atsEntityAclAssignees for members who can view the jobs.