Get LinkedIn import coverage for a file (internal)

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}/import-jobs/coverage

Extraction plumbing: reports which data types and conversations of an uploaded LinkedIn export file have already been imported into this case, combined across its completed import jobs. Returns 404 if the file is not found.

Path parameters

  • caseId string Required

Query parameters

  • fileId string Required

    UserFile ID of the uploaded zip to report coverage for

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
    • data object Required
      Hide data attributes Show data attributes object
      • fileId string Required

        UserFile ID the coverage is reported for

      • importedAllDataTypes boolean Required

        True when a prior job imported every data type

      • importedDataTypes array[string] Required

        Union of data types imported across completed jobs

      • importedAllConversations boolean Required

        True when a prior job imported every conversation

      • importedConversationIds array[string] Required

        Union of conversation IDs imported across completed jobs

    • statusCode number Required
    • timestamp string(date-time) Required
GET /linkedin/{caseId}/import-jobs/coverage
curl \
 --request GET 'http://api.example.com/linkedin/{caseId}/import-jobs/coverage?fileId=string' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
{
  "data": {
    "fileId": "string",
    "importedAllDataTypes": true,
    "importedDataTypes": [
      "string"
    ],
    "importedAllConversations": true,
    "importedConversationIds": [
      "string"
    ]
  },
  "statusCode": 200,
  "timestamp": "2026-01-15T10:15:00.000Z"
}