LinkedIn Search API
API health
- 24h health
- 97%
- 24h average time
- 9.72 s
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Find LinkedIn posts that match a keyword, with author, text, reactions and engagement counts, optionally limited by posting date and sorted by newest or relevance. Private posts, messages and reach analytics are out of scope.
LinkedIn Search finds public LinkedIn posts by keyword and returns each post's text, author name and username, like and comment counts, link and publish time. It shows who is talking about a topic on LinkedIn and how much engagement the conversation draws. B2B marketers and PR teams use it for social listening and tracking mentions of a brand or product, and sales teams use it to find people who post about a problem they solve.
Narrow results by publish time with date_range, from the past hour to the past month, and choose newest or relevance in sort. It searches posts only; people are found with LinkedIn Profile search and job postings with LinkedIn Jobs. A null like_count or comment_count means the number was not disclosed, not that it is zero, and author_username can usually be used to build the author's LinkedIn link.
Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra LinkedIn Search endpoint (linkedin/search).
Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to linkedin and action to search, and put the parameters inside params.
- Required parameters:
- keyword: Specifies the search string, acting as a post search keyword in search, a current job title in profile_search, or a job search term or full job URL in jobs.
- Optional parameters:
- date_range: Filters post publishing timestamps for the search action using allowed values no_filter, past_1_hour, past_24_hours, past_week, or past_month. (allowed: no_filter / past_1_hour / past_24_hours / past_month / past_week)
- sort: Sets the sorting order to newest or relevance for post search and comment fetching. Because these actions target different object types, this parameter does not sort people, companies, or job listings. (allowed: newest / relevance)
- limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 10)
- Returns a list of records. Main fields of each record: id, url, text, author_name, author_username, author_headline, author_id (Numeric member ID of the post author (s…), author_url (Profile link of the post author (search…), author_avatar_url (Avatar link of the post author (search)), reactions (Reaction counts by type (search): each…), attachment (Card attached to the post (search): typ…), like_count; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=linkedin.
- Example request body:
{
"platform": "linkedin",
"action": "search",
"params": {
"keyword": "data engineer"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | linkedin | Platform identifier, fixed value. |
action | body | string | Yes | search | Capability identifier, fixed value. |
keyword | body.params | Not declared | Yes | - | Specifies the search string, acting as a post search keyword in search, a current job title in profile_search, or a job search term or full job URL in jobs. Searching for people with this parameter does not perform an exact match by individual name or email. |
date_range | body.params | enum | No | - | Filters post publishing timestamps for the search action using allowed values no_filter, past_1_hour, past_24_hours, past_week, or past_month. It applies strictly to post publishing times rather than job listing validity or personal employment history.Allowed valuesno_filterpast_1_hourpast_24_hourspast_monthpast_week |
sort | body.params | enum | No | - | Sets the sorting order to newest or relevance for post search and comment fetching. Because these actions target different object types, this parameter does not sort people, companies, or job listings.Allowed valuesnewestrelevance |
limit | body.params | integer (1–50) | No | 10 | The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "linkedin",
"action": "search",
"params": {
"keyword": "data engineer"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
{
"id": "req_…",
"platform": "linkedin",
"action": "search",
"results": [
{
"id": "(已隐去)",
"url": "https://www.linkedin.com/posts/triveni-p-186b23245_hiring-immediatejoiners-itjobs-activity-7509276127224463360-gDVu?utm_source=social_share_send&utm_medium=member_desktop_web&rcm=ACoAAG7RZS4Be0lZ9Txw3UPxtvjwYlh3m2T4qFQ",
"text": "🚀 MULTIPLE IT OPENINGS | NOW HIRING\nHi All! 👋\nWe are looking for immediate to 15-day joiners for the below opportunities:\n📌 Open Positions\n▪️ Full Stack Data Engineer – 6–9 Yrs\n▪️ ETL + Automation Tester – 7–10 Yrs\n▪️ Informatica IDMC / MDM Consultant – 6+ Yrs\n▪️ GCP Data Enginee…",
"author_name": "(已隐去)",
"author_username": "(已隐去)",
"like_count": 11,
"comment_count": 0,
"posted_at": "2026-09-25T17:42:24+00:00",
"platform": "linkedin"
},
{
"id": "(已隐去)",
"url": "https://www.linkedin.com/posts/swapnilbandgar_dataengineer-hiring-aws-activity-7509255941473841153-s1yJ?utm_source=social_share_send&utm_medium=member_desktop_web&rcm=ACoAAG7RZS4Be0lZ9Txw3UPxtvjwYlh3m2T4qFQ",
"text": "We’re hiring! Looking for a Data Engineer to join our team.\n📍 Location: Pune (Hybrid - 3 days/week)\n💻 Tech Stack: SQL, Python, AWS\n📈 Experience: 4+ years hands-on\n\nInterested? Shoot me a DM or tag someone who might be a great fit!\n\n#DataEngineer #Hiring #AWS #Python #SQL",
"author_name": "(已隐去)",
"author_username": "(已隐去)",
"like_count": 19,
"comment_count": 3,
"posted_at": "2026-09-25T16:22:11+00:00",
"platform": "linkedin"
}
],
"count": 10,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
author_name | Author's display name. |
author_username | Author's username (@handle), usually usable in URLs. |
author_headline | Keeps the platform's own meaning |
author_id | Numeric member ID of the post author (search). |
author_url | Profile link of the post author (search), without tracking parameters. |
author_avatar_url | Avatar link of the post author (search). |
reactions | Reaction counts by type (search): each entry has type (like, appreciation, empathy and so on) and count. |
attachment | Card attached to the post (search): type (for example job or article), title, description, subtitle, url and image_url. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
comment_count | Comments. null means not disclosed, not 0. |
share_count | Number of times the post was reshared. |
hashtags | Hashtag list of the company page or post. |
is_reshare | Whether the post is a reshare of another post. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
Can this search people or jobs?
No, it searches posts. For people, use LinkedIn Profile search, which looks people up by current job title; for job postings, use LinkedIn Jobs, which takes a job search term or a LinkedIn job search URL. Each capability returns its own kind of record, so pick the one that matches what you want to count.
How do I get only the latest posts on a topic?
Set date_range to past_1_hour, past_24_hours, past_week or past_month, and sort to newest; no_filter applies no time window. The window applies to when posts were published, not to job validity or anyone's employment dates. Parse posted_at defensively, since non-standard time strings are passed through as is.
How do I read the comments on a post I found?
Pass the post's link from url to the LinkedIn Comments capability, which takes a full post link and returns the comments under it. comment_count tells you beforehand how many comments a post has, so you can skip posts that drew no discussion.
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).
Official references
Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- LinkedIn Official Documentation: Public, Connection-Visible, and Group Posts Have Distinct Visibility Boundaries ↗
Official documentation distinguishes post audiences among Anyone, Connections only, and Groups. This defines visibility limits for keyword searches and does not endorse custom date filtering or complete dataset coverage.
Checked 2026-09-04
- LinkedIn User Agreement: Restrictions on Scraping, Copying, and Reuse ↗
Section 8.2 of the User Agreement restricts automated scraping, circumventing access controls, and copying, using, displaying, or distributing content without consent from rights holders, including content obtained through third parties. Separate written permission requires independent confirmation, and public availability does not confer an exemption.
Checked 2026-09-04