LinkedIn: Community & Network icon

LinkedIn 数据 API:资料、职位、私信与访客

LinkedIn · 身份

LinkedIn 安卓端的每个界面都挂在登录会员记录上:GET /v1/account/me 返回 numeric plainId 与 MiniProfile;其他页面再以 GET /v1/profiles/{profileId} 加载完整资料、GET /v1/jobs/postings/{jobId} 水合职位卡片。

私信与访客数据同样走私有端点:GET /v1/messages/threads 分页返回会话列表,GET /v1/analytics/profile-views 返回谁看过我的资料卡片。

LinkedIn: Community & Network(包名 com.linkedin.android,应用版本 6.1.1)是 LinkedIn 的安卓客户端,覆盖会员资料、首页动态、职位、私信与谁看过我。其数据 API 以会话 Cookie 认证,围绕 profileId 等标识返回 JSON。

应用截图

  • LinkedIn: Community & Network 应用截图 1
  • LinkedIn: Community & Network 应用截图 2
  • LinkedIn: Community & Network 应用截图 3
  • LinkedIn: Community & Network 应用截图 4
  • LinkedIn: Community & Network 应用截图 5
  • LinkedIn: Community & Network 应用截图 6

API 端点一览

  • 获取登录会员(me)

    GET /v1/account/me osint

    返回其他所有界面依赖的登录会员记录:numeric plainId、MiniProfile 与账号状态。

    认证方式: Signed-in session cookie; CSRF token header mirrored from the session cookie; installation-id header; client-tracking JSON header (clientVersion, osName).

    • plainId
    • premiumSubscriber
    • realByEmerald
    • miniProfile
    • entityUrn
    • objectUrn
    • firstName
    • lastName
    • occupation
    • publicIdentifier
    • trackingId
    • publicContactInfo
    • twitterHandles

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/account/me HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    X-Client-Id: <installation-id>
    X-Client-Track: {"osName":"Android","clientVersion":"6.1.1","osVersion":"13","deviceModel":"Google_Pixel"}
    Cookie: session=<session-token>
    {
      "plainId": 123456789,
      "premiumSubscriber": false,
      "realByEmerald": true,
      "miniProfile": {
        "entityUrn": "urn:li:fs_miniProfile:ACoAAExample01",
        "objectUrn": "urn:li:member:123456789",
        "firstName": "Alex",
        "lastName": "Rivera",
        "occupation": "Product Manager at Example Corp",
        "publicIdentifier": "alex-rivera",
        "trackingId": "aq1b2c3d4e5=="
      },
      "publicContactInfo": {
        "twitterHandles": [{"name": "alexrivera"}]
      }
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the app's signed-in member bootstrap flow.
    • Field set matches the member record bound to the Me tab.
  • 获取会员资料

    GET /v1/profiles/{profileId} osint

    加载完整身份资料(姓名、头衔、行业、地区、简介、微信名片等字段)。

    认证方式: Signed-in session cookie; CSRF token header mirrored from the session; installation-id and client-tracking headers.

    • entityUrn
    • firstName
    • lastName
    • maidenName
    • headline
    • summary
    • industryName
    • industryUrn
    • locationName
    • geoCountryName
    • geoLocationName
    • address
    • phoneticFirstName
    • phoneticLastName
    • student
    • versionTag
    • weChatNameCardURL
    • miniProfile
    • publicIdentifier

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/profiles/ACoAAExample01 HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    X-Client-Id: <installation-id>
    Cookie: session=<session-token>
    {
      "entityUrn": "urn:li:fs_profile:ACoAAExample01",
      "firstName": "Alex",
      "lastName": "Rivera",
      "maidenName": "",
      "headline": "Product Manager at Example Corp",
      "summary": "Building identity products.",
      "industryName": "Software Development",
      "industryUrn": "urn:li:fs_industry:4",
      "locationName": "San Francisco Bay Area",
      "geoCountryName": "United States",
      "geoLocationName": "San Francisco, California, United States",
      "address": "San Francisco, CA",
      "phoneticFirstName": "Alex",
      "phoneticLastName": "Rivera",
      "student": false,
      "versionTag": "1234567890",
      "weChatNameCardURL": "",
      "miniProfile": {
        "publicIdentifier": "alex-rivera",
        "occupation": "Product Manager at Example Corp"
      }
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the profile screen's data binding.
    • Public profile deep links resolve through the same resource.
  • 获取资料联系方式

    GET /v1/profiles/{profileId}/contact osint

    返回资料的私有联系卡片——邮箱、电话、网站、Twitter 账号等。

    认证方式: Signed-in session cookie; CSRF token header. The contact payload is gated by the viewer's relationship to the profile.

    • entityUrn
    • emailAddress
    • address
    • connectedAt
    • phoneNumbers
    • number
    • extension
    • type
    • websites
    • twitterHandles
    • weChatContactInfo
    • name
    • weChatHandle
    • qr
    • qrCodeImageUrl
    • birthDateOn
    • birthdayVisibilitySetting

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/profiles/ACoAAExample01/contact HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    Cookie: session=<session-token>
    {
      "entityUrn": "urn:li:fs_profileContactInfo:ACoAAExample01",
      "emailAddress": "[email protected]",
      "address": "San Francisco, CA",
      "connectedAt": 1609459200000,
      "phoneNumbers": [
        {"number": "+15555550100", "extension": "", "type": "MOBILE"}
      ],
      "websites": [{"url": "https://example.com"}],
      "twitterHandles": [{"name": "alexrivera"}],
      "weChatContactInfo": {
        "name": "Alex Rivera",
        "weChatHandle": "alex_rivera",
        "qr": "weixin://contacts/profile/alex_rivera",
        "qrCodeImageUrl": "https://cdn.example.com/wechat/qr.png"
      },
      "birthDateOn": {"month": 4, "day": 12},
      "birthdayVisibilitySetting": "CONNECTIONS"
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the contact-info sheet shown after a connection is accepted.
    • Payload visibility varies with the viewer's relationship to the profile.
  • 获取职位详情

    GET /v1/jobs/postings/{jobId} opendata

    水合单个职位卡片(标题、地点、发布状态、远程标记、申请 / 收藏状态等)。

    认证方式: Signed-in session cookie; CSRF token header; client-tracking header.

    • entityUrn
    • title
    • formattedLocation
    • listedAt
    • closedAt
    • jobState
    • listingType
    • workRemoteAllowed
    • talkToRecruiterEnabled
    • sourceDomain
    • applyingInfo
    • savingInfo
    • companyDetails
    • company
    • companyResolutionResult

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/jobs/postings/4123456789 HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    Cookie: session=<session-token>
    {
      "entityUrn": "urn:li:fs_normalized_jobPosting:4123456789",
      "title": "Staff Product Manager",
      "formattedLocation": "San Francisco, CA",
      "listedAt": 1759276800000,
      "closedAt": 0,
      "jobState": "LISTED",
      "listingType": "PREMIUM",
      "workRemoteAllowed": true,
      "talkToRecruiterEnabled": true,
      "sourceDomain": "example.com",
      "applyingInfo": {"applied": false},
      "savingInfo": {"saved": false},
      "companyDetails": {
        "company": "urn:li:fs_miniCompany:1337",
        "companyResolutionResult": {"name": "Example Corp"}
      }
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the job detail card flow.
    • Saved and applied job lists query the same posting resource.
  • 列出私信会话

    GET /v1/messages/threads osint

    分页返回登录用户的收件箱(会话 urn、参与者 MiniProfile、未读数、免打扰 / 归档状态)。

    认证方式: Signed-in session cookie; CSRF token header. Collection paging via start/count.

    • elements
    • entityUrn
    • backendUrn
    • name
    • read
    • muted
    • archived
    • blocked
    • unreadCount
    • totalEventCount
    • withNonConnection
    • notificationStatus
    • participants
    • miniProfile
    • paging
    • start
    • count
    • total

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/messages/threads?start=0&count=20 HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    Cookie: session=<session-token>
    {
      "elements": [
        {
          "entityUrn": "urn:li:fs_conversation:2-YWM5YzA=",
          "backendUrn": "urn:li:messagingThread:2-YWM5YzA=",
          "name": "Alex Rivera, Sam Lee",
          "read": false,
          "muted": false,
          "archived": false,
          "blocked": false,
          "unreadCount": 2,
          "totalEventCount": 18,
          "withNonConnection": false,
          "notificationStatus": "ACTIVE",
          "participants": [
            {
              "miniProfile": {
                "firstName": "Sam",
                "lastName": "Lee",
                "publicIdentifier": "sam-lee",
                "occupation": "Recruiter at Example Corp"
              }
            }
          ]
        }
      ],
      "paging": {"start": 0, "count": 20, "total": 42}
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the inbox conversation list flow.
    • Collection paging follows an offset/count convention.
  • 列出谁看过我的资料

    GET /v1/analytics/profile-views opendata

    返回 Who Viewed My Profile 卡片(访客 MiniProfile 或匿名化访客、viewedAt 等)。

    认证方式: Signed-in session cookie; CSRF token header. Viewer identity is full or obfuscated depending on subscription tier.

    • elements
    • viewedAt
    • referrer
    • pendingInvitee
    • showInMailCta
    • openProfile
    • viewer
    • profile
    • occupation
    • insights
    • timeRange
    • paging

    依据应用界面重构的示意示例,并非实时抓包。

    GET /v1/analytics/profile-views?start=0&count=10 HTTP/1.1
    Accept: application/json
    X-CSRF-Token: <csrf-token>
    Cookie: session=<session-token>
    {
      "elements": [
        {
          "viewedAt": 1759276800000,
          "referrer": "SEARCH",
          "pendingInvitee": false,
          "showInMailCta": true,
          "openProfile": true,
          "viewer": {
            "type": "FULL",
            "profile": {
              "firstName": "Sam",
              "lastName": "Lee",
              "publicIdentifier": "sam-lee"
            },
            "occupation": {"name": "Recruiter at Example Corp"}
          },
          "insights": [{"text": "Works at Example Corp"}]
        }
      ],
      "metadata": {"timeRange": {"start": 1756684800000, "end": 1759276800000}},
      "paging": {"start": 0, "count": 10, "total": 27}
    }

    依据应用界面推导;端点细节为示意说明,并非实际抓包。

    • Reconstructed from the Who Viewed My Profile analytics screen.
    • Viewer identity resolves to a full or obfuscated profile depending on subscription tier.

数据类别

  • 用户资料
  • 联系方式
  • 职位
  • 私信
  • 资料浏览
  • 人脉

数据使用场景与案例

  • 招聘寻访副驾

    寻访工具抓取会员档案、档案联系方式与在招职位,拼出候选人短名单——头衔、行业、所在地与触达渠道合为一条记录。

  • 个人 CRM 同步

    面向创始人与销售的 CRM 镜像消息会话与「谁看过我」动态,把档案访问和未读会话转成跟进任务。

  • 招聘市场监测

    市场研究管道持续跟踪职位发布——发布/关闭时间、是否支持远程、招聘方——绘制各行业在哪些地区扩招。

常见问题

LinkedIn 安卓端使用什么数据 API?

应用调用一套私有 JSON API:GET /v1/account/me 返回登录会员,GET /v1/profiles/{profileId} 加载资料;职位、私信与访客各有端点,全部以会话 Cookie 认证。

该 API 如何认证?

所有端点依赖登录后的会话 Cookie(li_at 等),没有公开的开发者密钥;这是官方应用登录后使用的第一方接口。

能否程序化读取职位信息?

应用内的职位卡片由 GET /v1/jobs/postings/{jobId} 驱动,返回标题、地点、发布状态、远程标记与申请 / 收藏状态;它是需要会话的私有端点,不是公开 API。

谁看过我的数据来自哪个端点?

GET /v1/analytics/profile-views 返回访客卡片(访客 MiniProfile 或匿名化访客、viewedAt 时间等),按会员可见性规则决定是否暴露访客身份。

相关主题

  • linkedin api
  • LinkedIn 资料接口
  • linkedin member endpoint
  • LinkedIn 职位 API
  • linkedin messaging api
  • 谁看过我接口
  • linkedin 联系方式字段
  • 会话 Cookie 认证
  • MiniProfile

需要集成这个 App 的数据 API?

我们可为任意指定 App 交付定制集成——源码交付 USD 500 起,或托管 API 按调用计费。告诉我们您需要的数据即可。

获取报价