Member Snapshot API
Once the member has consented to share data and an access token is generated, Linkedin processes historical LinkedIn data for the member. Developers can query this data using the Member Snapshot API.
Note
Member Snapshot API uses the Versioned LinkedIn APIs. Please append the header LinkedIn-Version: 202312
while making the API requests.
Usage
You must use an access token to make an authenticated call on behalf of a user.
Permissions
Permission | Description |
---|---|
r_dma_portability_3rd_party | Provides access to LinkedIn member data to developers upon member authorization |
r_dma_portability_member | Allows users to download their own LinkedIn data |
Query Member Snapshot data
The following request can be used to query snapshot data for a user:
Query Parameters
Field Name | Required | Description |
---|---|---|
domain | No | Represents the particular domain of data being requested. If no specific domain if provided, the response contains data from all domains. For a complete list of domains refer here. |
The Member Shapshot API returns an array of elements with the following schema.
Member Snapshot Schema
Field Name | Format | Description |
---|---|---|
snapshotDomain | Enum | The type of LinkedIn data processed for the user. For a detailed list of domains supported, refer here. |
snapshotData | JSON Key Value | Data processed for the user |
Sample Get Response
{
"paging": {
"start": 0,
"count": 10,
"links": [
{
"type": "application/json",
"rel": "next",
"href": "/rest/memberSnapshotData?count=10&domain=PROFILE&q=criteria&start=1"
}
],
"total": 2
},
"elements": [
{
"snapshotData": [
{
"Websites": "",
"Address": "",
"Maiden Name": "",
"Instant Messengers": "",
"First Name": "Tom",
"Geo Location": "",
"Twitter Handles": "",
"Industry": "",
"Zip Code": "94086",
"Headline": "Marketing Manager at Microsoft, Inc.",
"Summary": "",
"Birth Date": "",
"Last Name": "Cruise"
}
],
"snapshotDomain": "PROFILE"
}
]
}
Note
In the response elements
field will always contain exactly 1 element with snapshotDomain
specifying domain. The snapshotData
field would be a list with data generated for the specific domain.
Response Pagination
The response can contain a lot of information depending on the domain
specified in the request. In order to reduce latency the response may be paginated where the snapshotData
is divided across multiple pages. If the response is paginated and the data is divided into multiple pages, the paging
field will contain links to access the next
and prev
pages. The start
query parameter determines which page you want to fetch.
Note
The "total" count field may not fully reflect the total number of pages to be retrieved as some data is retrieved through offline systems. Please continue looping through the pages until you receive an error message indicating "No data found for this memberId".
Sample Paginated response with paging information.
{
"paging": {
"start": 1,
"count": 10,
"links": [
{
"type": "application/json",
"rel": "prev",
"href": "/rest/memberSnapshotData?q=criteria&start=0&domain=GROUP_POSTS"
},
{
"type": "application/json",
"rel": "next",
"href": "/rest/memberSnapshotData?q=criteria&start=2&domain=GROUP_POSTS"
}
],
"total": 16
},
"elements" :{
...
}
}