Skip to main content

Data Retrieval

Retrieving person data

This page describes how to create workflows for retrieving various types of LinkedIn person data, including basic information, experience, education, and more.

Retrieving basic info

To retrieve basic information about a person, you need to include openPersonPage action in your workflow, with basicInfo parameter set to true. Here's an example:

Workflow:


{
  "actionType": "openPersonPage",
  "personUrl": "https://www.linkedin.com/in/person1",
  "basicInfo": true
}

Completion:


{
  "actionType": "openPersonPage",
  "success": true,
  "data": {
    "name": "John Doe",
    "publicUrl": "https://www.linkedin.com/in/person1",
    "hashedUrl": "https://www.linkedin.com/in/SInQBmjJ015eLr8",
    "headline": "Software Engineer at TechCorp",
    "location": "San Francisco, USA",
    "countryCode": "US",
    "position": "Software Engineer",
    "companyName": "TechCorp",
    "companyHashedUrl": "https://www.linkedin.com/company/12345678"
  }
}

Retrieving experience

To retrieve information about a person's experience, you need to include retrievePersonExperience action as a child of openPersonPage. Here's an example:

Workflow:


{
  "actionType": "openPersonPage",
  "personUrl": "https://www.linkedin.com/in/person1",
  "basicInfo": false,
  "then": [
    {
      "actionType": "retrievePersonExperience"
    }
  ]
}

Completion:


{
  "actionType": "openPersonPage",
  "success": true,
  "data": {
    "then": [
      {
        "actionType": "retrievePersonExperience"
        "success": true,
        "data": [
          {
            "position": "Software Engineer",
            "companyName": "TechCorp",
            "companyHashedUrl": "https://www.linkedin.com/company/12345678",
            "employmentType": "fullTime",
            "locationType": "onSite",
            "description": "Developing innovative software solutions.",
            "duration": 24,
            "startTime": "2021-01-01T00:00:00Z",
            "endTime": null,
            "location": "San Francisco, USA"
          },
          {
            "position": "Junior Developer",
            "companyName": "CodeBase Inc.",
            "companyHashedUrl": "https://www.linkedin.com/company/87654321",
            "employmentType": "internship",
            "locationType": "remote",
            "description": "Worked on front-end development tasks.",
            "duration": 12,
            "startTime": "2020-01-01T00:00:00Z",
            "endTime": "2020-12-31T00:00:00Z",
            "location": null
          }
        ]
      }
    ]
  }
}

Retrieving education

To retrieve information about a person's education, you need to include retrievePersonEducation action as a child of openPersonPage. Here's an example:

Workflow:


{
  "actionType": "openPersonPage",
  "personUrl": "https://www.linkedin.com/in/person1",
  "basicInfo": false,
  "then": [
    {
      "actionType": "retrievePersonExperience"
    },
    {
      "actionType": "retrievePersonEducation"
    }
  ]
}

Completion:


{
  "actionType": "openPersonPage",
  "success": true,
  "data": {
    "then": [
      {
        "actionType": "retrievePersonExperience"
        "success": true,
        "data": [ ... ]
      },
      {
        "actionType": "retrievePersonEducation"
        "success": true,
        "data": [ 
          {
            "schoolName": "Harvard University",
            "schoolHashedUrl": "https://www.linkedin.com/company/12345678",
            "details": "Master of Science in Computer Science, Artificial Intelligence"
          },
          {
            "schoolName": "MIT",
            "schoolHashedUrl": "https://www.linkedin.com/company/87654321",
            "details": "Bachelor of Science in Electrical Engineering and Computer Science"
          }
        ]
      }
    ]
  }
}

Retrieving other data

To retrieve other types of person data, you can use the following actions as children of openPersonPage (just as in the examples above):

This page provides examples of workflows and their completions. For detailed documentation on constraints, parameters, and possible results of specific actions, always refer to the corresponding action documentation pages.