Scrape content posted by LinkedIn users.
Endpoint: POST https://api.skillboss.co/v1/run · Model: linkedin-post-scraper
Use cURL when you want the clearest raw HTTP example. This is the fastest way to validate auth, inputs, output shape, and the canonical endpoint before wiring the API into code or agent workflows.
curl -X POST https://api.skillboss.co/v1/run \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "linkedin-post-scraper",
"inputs": {
// Your parameters here
}
}'Extract structured data from public websites
Automate repetitive research and monitoring
Feed fresh web data into AI agents and workflows
LinkedIn Post Scraper is a scraping api available through SkillBoss. Teams use it to add LinkedIn Post Scraper to apps, automations, and AI agent workflows without managing separate vendor credentials. This page gives both humans and agents one stable place to understand the capability, pricing path, and invocation pattern before they ship it into production.
Send a POST request to https://api.skillboss.co/v1/run with "model": "linkedin-post-scraper" and an "inputs" object. SkillBoss handles auth, billing, and the unified API layer. If you are testing the endpoint manually, start with the cURL or Python tab below. If you are wiring an autonomous agent, use the x402 or MPP tabs when the payment path matters.
SkillBoss gives you one API key, pay-as-you-go billing, and a consistent integration flow across many APIs. That reduces setup time and makes the endpoint easier to use in Claude Code, Cursor, Windsurf, and other agents. It also gives you a canonical public page, consistent docs, and one billing surface instead of forcing each team to juggle provider-specific auth and pricing rules.
Yes. This page is designed as a discovery surface for both humans and agents: clear capability framing, direct code examples, and a stable canonical URL make it easier to find, evaluate, and invoke. The structure is deliberate so search engines, agent runtimes, and developers can all understand what the endpoint does, how it is paid for, and which next pages matter.
LinkedIn Post Scraper is better served through the standard SkillBoss API key flow. x402 and MPP work best when pricing is deterministic before execution, which is not the safest assumption for this endpoint.
One API key. 100+ models.
Call linkedin-post-scraper through SkillBoss — same endpoint, zero markup.