urlstringrequired
Full URL of the LinkedIn post to list comments for.
https://api.sandbase.ai/v1/api/linkedin/post-commentsList comments on a LinkedIn post - full text, commenter name/URL/job title, timestamps, and engagement.
Your output will appear here
Complete the inputs, then click Run.
List comments on a LinkedIn post - full text, commenter name/URL/job title, timestamps, and engagement.
curl -X POST "https://api.sandbase.ai/v1/api/linkedin/post-comments" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ", "limit": 10}'
The result is returned in outputs[0].data. A lookup that finds nothing still succeeds and returns found: false.
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Full URL of the LinkedIn post to list comments for. |
limit | integer | No | Maximum number of comments to return. Default 100. |
postedLimit | string | No | Only return comments posted within this window (default any). One of: any, 24h, week, month, 3months, 6months, year. |
Billed at the actual cost of each call, usually $0.0029 per request. A call can cost more when the first data source fails and another one answers. Failed calls are not charged. Lookups that find nothing and searches with no results are billed at their actual cost, which is often lower and can be $0.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/linkedin/post-comments" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://www.linkedin.com/posts/stripe_philip-kl%C3%B6ckner-in-conversation-with-conor-activity-7477791740645564416-tIbZ",
"limit": 10
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
urlstringrequiredFull URL of the LinkedIn post to list comments for.
limitintegerMaximum number of comments to return.
Default: 100
postedLimitstringOnly return comments posted within this window (default any).
Possible values: any, 24h, week, month, 3months, 6months, year
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
LinkedIn Post CommentsThis API LinkedIn | From $0.0029 per call | JSON |
LinkedIn | From $0.0012 per call | JSON |
LinkedIn | From $0.03 per call | JSON |
LinkedIn | From $0.0012 per call | JSON |
LinkedIn | From $0.0057 per call | JSON |
LinkedIn | From $0.0026 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/linkedin/post-comments with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
From $0.0029 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: url (string). Optional: limit (integer) and postedLimit (one of any, 24h, week, month, 3months, 6months, year). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. LinkedIn Post Comments runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for LinkedIn API access separately.