docs(social): posts param now covers LinkedIn#260
Conversation
…ment) When posts is requested, LinkedIn scrapes return the profile's latest N posts with like/comment/share counts and a reaction-type breakdown (harvestapi/linkedin-profile-posts), instead of ignoring the parameter. Contract for recoupable/chat#1838; api implementation follows. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
…ested (#745) A requested posts depth switches the LinkedIn scrape from harvestapi/linkedin-profile-scraper (whose dataset has zero post fields) to harvestapi/linkedin-profile-posts with {targetUrls, maxPosts} — post items with engagement counts (likes, comments, shares, reaction breakdown). posts omitted keeps the profile actor with byte-identical input. Same handle guards, URL normalization, webhooks, and error paths. Matches X/YouTube semantics (depth → post items; omitted → snapshot). Actor verified live 2026-07-02: run aKsHPucJ3thxuosSd, 5 posts @ $0.01005 ($0.002/post) — the shipped 5 + posts credit rule covers it at ~5x margin, no billing change. Implements recoupable/chat#1838; contract in recoupable/docs#260. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
1 participant
Summary
Contract PR for recoupable/chat#1838 — merge before the api PR.
Both scrape endpoints'
postsdescriptions now state LinkedIn returns the profile's latest N posts with like/comment/share counts and a reaction-type breakdown (backed byharvestapi/linkedin-profile-posts, verified live: runaKsHPucJ3thxuosSd, 5 items @ $0.01005). LinkedIn leaves the "other platforms ignore this parameter" bucket; Instagram/TikTok/etc. remain in it. No pricing change — the shipped 5 + posts credit rule covers LinkedIn at ~5× margin ($0.002/post).Both files re-parse; diff is two description strings.
🤖 Generated with Claude Code
Summary by cubic
Documented LinkedIn support for the
postsquery parameter in social scrape endpoints. When set, LinkedIn returns the profile’s latest N posts with like, comment, and share counts plus a reaction-type breakdown; other platforms’ behavior is unchanged.Written for commit b98c48d. Summary will update on new commits.