Share via

Module 3 - Retrieve Data from LinkedIn

Note

There are some updates to test cases and hence you might not see a few of them.

Test Case 6 - One-Click Export (New Candidate)

Execution Steps
  1. Export a profile from LinkedIn Recruiter to a job requisition in your ATS
Expected Result
  1. Ensure the candidate appears in the ATS as a candidate for that job
  2. View Profile Widget within the ATS and ensure exact match displays

Relevant Documentation: Retreive Exported Candidates

Test Case 7 - Export update test (Existing Candidate)

Execution Steps
  1. Edit the ATS record for the candidate exported in the prior step. Export the same candidate to a different job
Expected Result
  1. Confirm the candidate is not duplicated
  2. Confirm the candidate is associated to both jobs

Relevant Documentation: Retreive Exported Candidates

Test Case 8 - Manual Profile Link Test

Execution Steps
  1. Add a candidate to the ATS which does not match a profile on LinkedIn by inventing a name and email address
  2. In the ATS Profile Plugin, manually link this new candidate to a complete LinkedIn profile
Expected Result
  1. Refresh the page and ensure that the chosen LinkedIn profile is still displayed in the Profile Widget
  2. Ensure that the ATS candidate and LinkedIn profile mappings are updated

Relevant Documentation: Profile Plugin & Attach Person URN to Candidate

Test Case 9 - Login / Logout Test

Execution Steps
  1. Logout of LinkedIn, display the candidate Profile Widget
  2. Login to LinkedIn, display the candidate Profile Widget
Expected Result
  1. Ensure Sign In to LinkedIn widget is displayed.
  2. Ensure that scrolling in the Enhanced ATS Profile Widget fits within ATS UI

Relevant Documentation: Profile Plugin

Test Case 10 - InMail History Test

Execution Steps
  1. As a recruiter, send an InMail to a LinkedIn member (1st Connection) from a Recruiter account
  2. As a candidate, (recipient of InMail) reply to InMail
  3. In ATS, display the InMail conversation
Expected Result
  1. Call the LinkedIn REST API, ensure the pagination is used to get all results retrieving a history of received and sent InMails from Recruiter and ensure that the InMail appears in the results

Relevant Documentation: Retrieve InMail History

Test Case 11 - Stub Profile Based On InMail Response Test

Execution Steps
  1. As a recruiter, send an InMail to a LinkedIn member (1st connection not currently in ATS) on your team from a Recruiter
  2. As a candidate, (recipient of InMail) reply to InMail and share contact email
  3. Display new ATS candidate record
  4. As a recruiter, send an InMail to same LinkedIn member
  5. As a candidate, (recipient of InMail) reply to InMail and share a different contact email and phone number
  6. Display existing ATS candidate record has been updated
Expected Result
  1. Call the LinkedIn REST API, ensure the pagination is used to get all results of stub profiles. Ensure the values for all fields match, including: LinkedIn unique identifier, name, title, company, region, email address, and phone number (if applicable)
  2. If a new candidate - create a new record
  3. If an existing candidate - update an existing record if applicable

Relevant Documentation: Retrieve InMail Stub Profiles

Test Case 12 - Retrieve Seat Holders API

Execution Steps

To retrieve contract seat holders, use the below API

GET https://api.linkedin.com/v2/seatsV2?q=attributes&contracts=urn:li:contract:123456789&start=0&count=10

Expected result:

  1. If you are implementing the above API, make sure to use the seatsV2 API along with pagination as explained above. Show us the code snippet/screenshot of the codebase where above API is used to confirm that pagination and v2 api version is used.

Test Case 13 - Retrieve Closed Candidate Profiles

Execution Steps
  1. Demo where customers will see or be notified of (and have the option to delete) any LinkedIn member profiles that were deleted from LinkedIn after the customer 1-Click Exported the relevant profile
  2. Optional: Provide customers the option to delete 1-Click Exported LinkedIn member data globally or at member level (for example, LinkedIn Profile URL)
Expected Result
  1. Ensure that the list of deleted profiles displayed to the customer matches the list retrieved from LinkedIn. Ensure that any profiles deleted by the customer are removed from the ATS

Relevant Documentation: Retrieving Closed Candidate Profiles

Note

Once the candidate profile is closed it takes 21 days for the API to return the value. In case you cannot wait for 21 days to get certified, you can call a stub/mock API to demonstrate how ATS will handle the URNs returend in response. Upon receiving the real candidate data returned by LinkedIn API, a recording can be submitted to your Business Development point of contact with an end to end flow.