LinkedIn Comments API
API health
- 24h health
- Normal
- 24h average time
- —
- Last checked
- September 26, 2026 at 18:04 (UTC)
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
How health is measured
- Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
- Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
- A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
- Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
- Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
| Time (UTC) | Status | Health | Average time |
|---|---|---|---|
| 2026-09-26 18:00 - 18:59 | Normal | — | — |
| 2026-09-26 17:00 - 17:59 | Normal | — | — |
| 2026-09-26 16:00 - 16:59 | Normal | — | — |
| 2026-09-26 15:00 - 15:59 | Normal | — | — |
| 2026-09-26 14:00 - 14:59 | Normal | — | — |
| 2026-09-26 13:00 - 13:59 | Normal | — | — |
| 2026-09-26 12:00 - 12:59 | Normal | — | — |
| 2026-09-26 11:00 - 11:59 | Normal | — | — |
| 2026-09-26 10:00 - 10:59 | Normal | — | — |
| 2026-09-26 09:00 - 09:59 | Normal | — | — |
| 2026-09-26 08:00 - 08:59 | Normal | — | — |
| 2026-09-26 07:00 - 07:59 | Normal | — | — |
| 2026-09-26 06:00 - 06:59 | Normal | — | — |
| 2026-09-26 05:00 - 05:59 | Normal | — | — |
| 2026-09-26 04:00 - 04:59 | Normal | — | — |
| 2026-09-26 03:00 - 03:59 | Normal | — | — |
| 2026-09-26 02:00 - 02:59 | Normal | — | — |
| 2026-09-26 01:00 - 01:59 | Normal | — | — |
| 2026-09-26 00:00 - 00:59 | Normal | — | — |
| 2026-09-25 23:00 - 23:59 | Normal | — | — |
| 2026-09-25 22:00 - 22:59 | Normal | — | — |
| 2026-09-25 21:00 - 21:59 | Normal | — | — |
| 2026-09-25 20:00 - 20:59 | Normal | — | — |
| 2026-09-25 19:00 - 19:59 | Normal | — | — |
| 2026-09-26 | Normal | — | — |
| 2026-09-25 | Normal | — | — |
| 2026-09-24 | Normal | — | — |
| 2026-09-23 | Normal | — | — |
| 2026-09-22 | Normal | — | — |
| 2026-09-21 | Normal | — | — |
| 2026-09-20 | Normal | — | — |
| 2026-09-19 | Normal | — | — |
| 2026-09-18 | Normal | — | — |
| 2026-09-17 | Normal | — | — |
| 2026-09-16 | Normal | — | — |
| 2026-09-15 | Normal | — | — |
| 2026-09-14 | Normal | — | — |
| 2026-09-13 | Normal | — | — |
| 2026-09-12 | Normal | — | — |
| 2026-09-11 | Normal | — | — |
| 2026-09-10 | Normal | — | — |
| 2026-09-09 | Normal | — | — |
| 2026-09-08 | Normal | — | — |
| 2026-09-07 | Normal | — | — |
| 2026-09-06 | Normal | — | — |
| 2026-09-05 | Normal | — | — |
| 2026-09-04 | Normal | — | — |
| 2026-09-03 | Normal | — | — |
| 2026-09-02 | Normal | — | — |
| 2026-09-01 | Normal | — | — |
| 2026-08-31 | Normal | — | — |
| 2026-08-30 | Normal | — | — |
| 2026-08-29 | Normal | — | — |
| 2026-08-28 | Normal | — | — |
Retrieve public comments from LinkedIn. Accepts these parameters: num_likes, sort, url, and num_comments. Returns these fields: author_url, author_username, author_name, and like_count.
Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Asynchronous by default: returns a job_id first; poll GET /api/v1/jobs/{job_id}.
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 | comments | Capability identifier, fixed value. |
url | body.params | Not declared | Yes | - | Specifies the full LinkedIn post URL used by the comments action to fetch comments for that post; company or personal profile URLs are not supported. For other endpoints offering URL compatibility inputs, required parameters like username or company must still be supplied. |
num_comments | body.params | Not declared | No | - | Provides a compatibility input for setting an upper cap on fetched comments rather than filtering for a minimum comment count. It is currently read only on select paths and is not guaranteed to truncate results in main requests. |
num_likes | body.params | Not declared | No | - | Provides a compatibility input for setting an upper cap on retrieved like data rather than filtering posts by a minimum number of likes. It does not serve as a stable post popularity filter. |
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–200) | No | 20 |
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": "comments",
"params": {
"url": "https://www.linkedin.com/posts/linkedin_no-is-a-complete-sentence-activity-7247998907798978560-J_hB"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "linkedin",
"action": "comments",
"results": [
{
"id": …,
"text": …,
"url": …,
"author_name": …,
"author_username": …,
"author_headline": …,
"author_url": …,
"like_count": …,
"reply_count": …,
"is_pinned": …,
"is_edited": …,
"posted_at": …,
"post_url": …,
"platform": …,
"language": …
}
],
"count": …,
"billing": { … },
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms. |
text | Body text with HTML removed. Long text may be truncated. |
url | Link to the record on the source platform. |
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_url | Link to the author's profile on the source platform. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
is_pinned | Keeps the platform's own meaning |
is_edited | Keeps the platform's own meaning |
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. |
post_url | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
language | Content language code (for example zh, en) as judged by the platform; it can be wrong. |
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
- Per-minute request limit reached. Wait for Retry-After and try again.
- 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: Post and Interaction Visibility Depends on Audience Settings ↗
The visibility of posts and interaction activity varies according to the author's audience settings. This documentation establishes boundaries on comment availability and does not prove the capability to bypass permissions for connections, groups, or hidden content.
Checked 2026-09-04