LinkedIn Post Search

Search for LinkedIn posts by keywords and filters. The sample response includes authors and comments. Use it in content discovery, monitoring, or research. Choose an implementation and check its published request fields, examples, and usage pricing before integrating.

Selected price
$0.004 / callPublished pricing
Sellers / implementations
2 / 2
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (15)
Keywords to search for in posts
Filter posts by author's profile URL(s) or public identifier(s) or profile ID(s) (comma-separated). Note: LinkedIn returns fewer results per profile when using post search. To extract all posts by a profile, use the /linkedin/profile-posts endpoint
Filter posts by this company URL(s) or company ID(s) (comma-separated). Note: LinkedIn returns fewer results per company when using post search. To extract all posts by a company, use the /linkedin/company-posts endpoint
List of LinkedIn companies where authors of posts work (comma-separated). It supports company URLs and IDs.
List of LinkedIn industry IDs of authors' companies (comma-separated). It supports industry IDs. Full list of industry IDs: https://github.com/HarvestAPI/linkedin-industry-codes-v2/blob/main/linkedin_industry_code_v2_all_eng.csv
Filter posts mentioning this LinkedIn profile URL or ID (comma-separated). It supports profile URLs and IDs.
Filter posts mentioning this LinkedIn company URL or ID (comma-separated). It supports company URLs and IDs.
Filter by content type. Supported values: 'videos', 'images', 'live_videos', 'documents', 'collaborative_articles', 'jobs'
Filter by keywords in authors' profiles
Group LinkedIn URL or Group ID
Filter posts by maximum posted date. Supported values: '24h', 'week', 'month'. This parameter will be sent to LinkedIn, the filtering will be done on their side
Post-Filter posts by maximum posted date. Supported values: '1h', '24h', 'week','month', '3months', '6months', 'year'. This parameter will be applied after receiving results from LinkedIn, the filtering will be done on our side
Sort by field. Supported values: 'relevance', 'date'
Page number for pagination
Required if it was returned by the previous page. Otherwise the page will always be 1 (on LinkedIn side). Doesn't apply for all queries, usually profile posts return this token

Sample response

{
  "elements": [
    {
      "article": {
        "description": "<description>",
        "image": {
          "expiresAt": 0,
          "height": 0,
          "url": "<url>",
          "width": 0
        },
        "link": "<link>",
        "linkLabel": "<linkLabel>",
        "subtitle": "<subtitle>",
        "title": "<title>"
      },
      "author": {
        "avatar": {
          "expiresAt": 0,
          "height": 0,
          "url": "<url>",
          "width": 0
        },
        "id": "<id>",
        "info": false,
        "linkedinUrl": "<linkedinUrl>",
        "name": "<name>",
        "publicIdentifier": "<publicIdentifier>",
        "type": false,
        "universalName": "<universalName>",
        "urn": "<urn>",
        "website": false,
        "websiteLabel": false
      },
      "content": "<content>",
      "engagement": {
        "comments": 0,
        "likes": 0,
        "reactions": [
          {
            "count": 0,
            "type": "<type>"
          }
        ],
        "shares": 0
      },
      "id": "<id>",
      "linkedinUrl": "<linkedinUrl>",
      "newsletterTitle": "<newsletterTitle>",
      "newsletterUrl": "<newsletterUrl>",
      "postImages": [
        {
          "expiresAt": 0,
          "height": 0,
          "url": "<url>",
          "width": 0
        }
      ],
      "postVideo": {
        "thumbnailUrl": "<thumbnailUrl>",
        "videoUrl": "<videoUrl>"
      },
      "postedAt": {
        "date": "<date>",
        "postedAgoShort": "<postedAgoShort>",
        "postedAgoText": "<postedAgoText>",
        "timestamp": 0
      },
      "repost": null,
      "repostId": "<repostId>",
      "repostedBy": {
        "linkedinUrl": "<linkedinUrl>",
        "name": "<name>",
        "publicIdentifier": "<publicIdentifier>"
      },
      "socialContent": {
        "hideCommentAction": false,
        "hideCommentsCount": false,
        "hideReactAction": false,
        "hideReactionsCount": false,
        "hideRepostsCount": false,
        "hideSendAction": false,
        "hideShareAction": false,
        "hideSocialActivityCounts": false,
        "hideViewsCount": false,
        "shareUrl": "<shareUrl>",
        "showContributionExperience": false,
        "showSocialDetail": false
      }
    }
  ],
  "error": "<error>",
  "pagination": {
    "pageNumber": 0,
    "pageSize": 0,
    "paginationToken": "<paginationToken>",
    "previousElements": 0,
    "totalElements": 0,
    "totalPages": 0
  },
  "query": {
    "companyId": "<companyId>",
    "page": 0,
    "postedLimit": "<postedLimit>",
    "profileId": "<profileId>",
    "search": "<search>",
    "sortBy": "<sortBy>"
  },
  "status": 0
}

Response result

Response structure

Inferred from examples
  • elementsobject[]
    • articleobject
      • descriptionstring
      • imageobject
        • expiresAtinteger
        • heightinteger
        • urlstring
        • widthinteger
      • linkstring
      • linkLabelstring
      • subtitlestring
      • titlestring
    • authorobject
      • avatarobject
        • expiresAtinteger
        • heightinteger
        • urlstring
        • widthinteger
      • idstring
      • infoboolean
      • linkedinUrlstring
      • namestring
      • publicIdentifierstring
      • typeboolean
      • universalNamestring
      • urnstring
      • websiteboolean
      • websiteLabelboolean
    • contentstring
    • engagementobject
      • commentsinteger
      • likesinteger
      • reactionsobject[]
        • countinteger
        • typestring
      • sharesinteger
    • idstring
    • linkedinUrlstring
    • newsletterTitlestring
    • newsletterUrlstring
    • postImagesobject[]
      • expiresAtinteger
      • heightinteger
      • urlstring
      • widthinteger
    • postVideoobject
      • thumbnailUrlstring
      • videoUrlstring
    • postedAtobject
      • datestring
      • postedAgoShortstring
      • postedAgoTextstring
      • timestampinteger
    • repostnull
    • repostIdstring
    • repostedByobject
      • linkedinUrlstring
      • namestring
      • publicIdentifierstring
    • socialContentobject
      • hideCommentActionboolean
      • hideCommentsCountboolean
      • hideReactActionboolean
      • hideReactionsCountboolean
      • hideRepostsCountboolean
      • hideSendActionboolean
      • hideShareActionboolean
      • hideSocialActivityCountsboolean
      • hideViewsCountboolean
      • shareUrlstring
      • showContributionExperienceboolean
      • showSocialDetailboolean
  • errorstring
  • paginationobject
    • pageNumberinteger
    • pageSizeinteger
    • paginationTokenstring
    • previousElementsinteger
    • totalElementsinteger
    • totalPagesinteger
  • queryobject
    • companyIdstring
    • pageinteger
    • postedLimitstring
    • profileIdstring
    • searchstring
    • sortBystring
  • statusinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use LinkedIn Post Search with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.