integrations

Get a LinkedIn profile

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://docs.usehearsay.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "integrations MCP server": {
    "url": "https://docs.usehearsay.com/mcp"
  }
}
Close
GET /linkedin/{caseId}/{linkedInId}
Access token

Returns one LinkedIn profile linked to the case; returns 404 if it is archived or not linked. On a case shared with opposing counsel, a profile the caller may not see returns 404.

Path parameters

  • caseId string Required
  • linkedInId string Required

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
    • data object Required
      Hide data attributes Show data attributes object
      • createdAt string(date-time) Required
      • updatedAt string(date-time) Required
      • id string Required
      • linkedInProfileUrl string Required
      • firstName string | null Required
      • lastName string | null Required
      • headline string | null Required
      • industry string | null Required
      • email string | null Required
      • summary string | null Required
      • geoLocation string | null Required
      • avatar object | null Required

        Not loaded by any route, so always null.

      • metadata object | null Required
      • deletedAt string(date-time) | null Required
      • deletedBy string | null Required
      • ocSharedStatus string | null

        Opposing-council only: whether this provider has been shared with the OL. null for OL/OG callers — same convention as every other item listing. Provider-level: every item under it shares this status, since approval here is all-or-nothing.

        Values are shared, pending, or not_gated.

    • statusCode number Required
    • timestamp string(date-time) Required
GET /linkedin/{caseId}/{linkedInId} 
curl \
 --request GET 'http://api.example.com/linkedin/{caseId}/{linkedInId}' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200) 
{
  "data": {
    "createdAt": "2026-01-15T14:30:00.000Z",
    "updatedAt": "2026-01-15T14:30:00.000Z",
    "id": "507f1f77bcf86cd799439011",
    "linkedInProfileUrl": "linkedin-export-jane-doe",
    "firstName": "Jane",
    "lastName": "Doe",
    "headline": "Operations Manager at Acme Corp",
    "industry": "Logistics and Supply Chain",
    "email": "jane.doe@example.com",
    "summary": "Operations leader with ten years in regional logistics.",
    "geoLocation": "Springfield, Illinois, United States",
    "avatar": {},
    "metadata": {
      "address": "123 Main St, Springfield, IL",
      "zipCode": "62701",
      "websites": "[PERSONAL:https://example.com]"
    },
    "deletedAt": "2026-05-04T09:42:00Z",
    "deletedBy": "string",
    "ocSharedStatus": "shared"
  },
  "statusCode": 200,
  "timestamp": "2026-01-15T10:15:00.000Z"
}