harvestapi_linkedin_post_search $0.005 per call
Search LinkedIn posts. Search LinkedIn posts by keywords, author, date range, and more. (HarvestAPI · LinkedIn)
For AI agents: call harvestapi_linkedin_post_search
POST https://toll402.dev/v1/p/harvestapi.linkedin.post.search
{
"search": "Microsoft",
"page": 1
}Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server:
npx -y toll402-mcp · remote https://toll402.dev/mcp.Input schema
{
"type": "object",
"properties": {
"search": {
"type": "string",
"description": "Keywords to search for in posts",
"examples": [
"Microsoft"
]
},
"profile": {
"type": "string",
"description": "Filter posts by author's profile URL (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"
},
"profileId": {
"type": "string",
"description": "Filter posts by author's profile ID or IDs (comma-separated). It's faster to search by ID. Note: LinkedIn returns fewer results per profile when using post search. To extract all posts by a profile, use the /linkedin/profile-posts endpoint"
},
"company": {
"type": "string",
"description": "Filter posts by this company URL or URLs (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"
},
"companyId": {
"type": "string",
"description": "Filter posts by company ID or IDs (comma-separated). It's faster to search by ID. Note: LinkedIn returns fewer results per company when using post search. To extract all posts by a company, use the /linkedin/company-posts endpoint"
},
"authorsCompany": {
"type": "string",
"description": "List of LinkedIn companies where authors of posts work (comma-separated). It supports company URLs and IDs."
},
"authorsIndustryId": {
"type": "string",
"description": "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"
},
"mentioningMember": {
"type": "string",
"description": "Filter posts mentioning this LinkedIn profile URL or ID (comma-separated). It supports profile URLs and IDs."
},
"mentioningCompany": {
"type": "string",
"description": "Filter posts mentioning this LinkedIn company URL or ID (comma-separated). It supports company URLs and IDs."
},
"contentType": {
"type": "string",
"description": "Filter by content type. Supported values: 'videos', 'images', 'live_videos', 'documents', 'collaborative_articles', 'jobs'"
},
"authorKeywords": {
"type": "string",
"description": "Filter by keywords in authors' profiles"
},
"group": {
"type": "string",
"description": "Group LinkedIn URL or Group ID"
},
"postedLimit": {
"type": "string",
"description": "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"
},
"scrapePostedLimit": {
"type": "string",
"description": "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"
},
"sortBy": {
"type": "string",
"description": "Sort by field. Supported values: 'relevance', 'date'"
},
"page": {
"type": "integer",
"description": "Page number for pagination",
"examples": [
1
]
},
"paginationToken": {
"type": "string",
"description": "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"
}
},
"additionalProperties": true,
"description": "Use only the declared query parameters, once each, without a request body. Results are provider-native: inspect element/elements and body status/error; HTTP 200 alone does not prove a hit. Empty results can still be charged."
}
MCP
{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}