LinkedIn post details API
One LinkedIn post or article by URL
Use the LinkedIn post details API to read public LinkedIn posts. One LinkedIn post or article by URL.
Request
Send your API key as a Bearer token. Replace YOUR_API_KEY with a key from your console.
curl "https://xtikapi.com/v1/linkedin/posts/detail?url=https%3A%2F%2Fexample.com%2Fpost%2F1" \
-H "Authorization: Bearer YOUR_API_KEY"import requests
response = requests.get(
"https://xtikapi.com/v1/linkedin/posts/detail",
params={"url":"https://example.com/post/1"},
headers={"Authorization": "Bearer YOUR_API_KEY"},
)
print(response.json())const response = await fetch("https://xtikapi.com/v1/linkedin/posts/detail?url=https%3A%2F%2Fexample.com%2Fpost%2F1", {
headers: { Authorization: "Bearer YOUR_API_KEY" },
});
console.log(await response.json());Parameters
| Name | Type | Required |
|---|---|---|
| url | string | required |
Response fields
Every platform returns the same post shape. A field the platform does not provide is named in meta.unavailable.
- id
- url
- text
- author
- createdAt
- likeCount
- commentCount
- shareCount
- viewCount
- cover
Example response
A sample payload that shows the shape. Values are made up.
{
"example": true,
"data": {
"id": "example-post",
"url": "https://example.com/post/example",
"text": "Example post",
"author": {
"id": "example-user",
"username": "example"
},
"createdAt": "2026-01-01T00:00:00Z",
"likeCount": 1
},
"meta": {
"request_id": "example",
"endpoint": "linkedin.posts.detail",
"normalized": true,
"unavailable": [],
"billing": {
"charged": true,
"amount": 0.02,
"balance": 4.98
}
}
}Error codes
Errors are not billed. Retry the ones marked yes. More in the API quickstart.
| Code | HTTP | Retry | Meaning |
|---|---|---|---|
| unauthorized | 401 | no | API key is missing, invalid, or revoked. |
| rate_limited | 429 | yes | Too many requests. |
| invalid_params | 422 | no | Request parameters are invalid. |
| price_exceeds_max | 402 | no | This call costs more than X-Max-Price. |
| insufficient_balance | 402 | no | Balance is too low for this call. |
| key_limit_reached | 402 | no | This API key has reached its spend limit. |
| idempotency_conflict | 409 | no | This Idempotency-Key was already used with different parameters. |
| idempotency_in_progress | 409 | yes | A request with this Idempotency-Key is still running. |
| response_too_large | 409 | no | The response is too large to store for a safe retry. |
| upstream_error | 502 | yes | The data provider returned an error. You were not charged. |
| upstream_timeout | 504 | yes | The data provider timed out. You were not charged. |
| internal_error | 500 | yes | Something went wrong on our side. You were not charged. |
| not_found | 404 | no | No such endpoint. |
Questions this API answers
Same call on other platforms
Change the platform word in the path. The request and the response shape stay the same.
More LinkedIn APIs
Questions
What does the LinkedIn post details API return?
A post object with the fields listed on this page. Missing provider fields are named in meta.unavailable.
When is the LinkedIn post details API billed?
This call costs $0.02 when the provider returns HTTP 200. An empty result is billed. Errors and timeouts are not billed.
What do I do if the provider returns an error?
The response has charged set to false. Read the error code and retry if the error says retry is true. Your balance is unchanged.
Where is this resource on another platform?
Use the links on this page for the same resource and action on other platforms. Change the platform word in the path.