LinkedIn post API
LinkedIn post data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.
- 1 documented endpoints
- GET /v1/linkedin/posts/{id}
Contract summary (English): Get a normalized LinkedIn post (capability linkedin.post)
- Normalized response entity
- linkedin/post
- capability
- linkedin.post
Every response also carries freshness (cache / default / live) and billing metadata.
Use cases
- Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
- Power moderation, research and monitoring workflows that need the original content plus engagement counts.
- Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.
Response fields
LinkedIn Post (normalized)
Normalized LinkedIn post — the ONLY upper-layer format; provider-private fields are dropped. Serves linkedin.post and the post lists of /v1/linkedin.
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Required | Platform-native post id (pk / activity id / message id / cell id). |
| platform | "linkedin" | Required | — |
| type | "post" | Required | — |
| author.id | string | Required | Author platform id. |
| author.username | string | Required | Author addressing key without leading @. |
| author.display_name | string | null | Required | Author display name. |
| author.verified | boolean | Required | — |
| text | string | null | Required | Post text (null for media-only posts). |
| created_at | string | Required | Post publish time, UTC RFC3339. |
| metrics.likes | integer | Required | Reaction (like) count. |
| metrics.comments | integer | Required | Comment count. |
| metrics.shares | integer | Required | Repost count. |
| attachments | object[] | Optional | Media attachments (max 8): photo urls and/or the video block. |
| fetched_at | string | Required | Normalization time of the stored snapshot (UTC). |
Field notes are shown in the contract's original English.
Response meta
| Field | Type | Required | Description |
|---|---|---|---|
| mode | cache | default | live | Required | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | Optional | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | Required | Which layer served the response (PRD §10). |
| stale | boolean | Optional | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | Required | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | Required | — |
Field notes are shown in the contract's original English.
Example request & response
/v1/linkedin/posts/{id}curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/linkedin/posts/1842951234567890123"{
"data": {
"id": "7255000000001001",
"platform": "linkedin",
"type": "post",
"author": {
"id": "6155000122",
"username": "meshdata-linkedin",
"display_name": "MeshData LinkedIn",
"verified": false
},
"text": "一条关于数据 API 的 LinkedIn 帖子。",
"created_at": "2026-09-16T11:20:00Z",
"metrics": {
"likes": 3120,
"comments": 96,
"shares": 18
},
"fetched_at": "2026-09-21T09:00:00Z"
},
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 0,
"source_layer": "upstream",
"stale": false
},
"billing": {
"amount_credits": 100,
"cache_hit": false
}
}
}Free demo
Create a free account, grab an API key and call this endpoint from the browser-based Playground.
Try it in the PlaygroundParameter tables, error codes and response semantics for this endpoint live in the API documentation.
Open the endpoint referenceFrequently asked questions
Which content fields are included?
The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.
Can I try this endpoint for free?
Yes — register an account, grab an API key and call it from the Playground in the console.
How is the post capability billed?
Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.
Pricing
Per-request credit billing with cache/live freshness options — current prices live on the pricing page.