LinkedIn Scraper API Guide

Scraping is asynchronous: submit a run → poll → fetch data. The full flow is in Quick Start; the shared response envelope / run state machine / billing / error codes are in Auth & Error Handling. This page only lists each endpoint's submit target fields and output fields.

Common Conventions

The submit body is always { "deliveryMode": "async", "recordLimit": 1000, "targets": [ … ] }; the fields of each targets[] element are listed in the "Target fields" table for each endpoint below. Submit returns HTTP 201 + { "code": 0, "message": "ok", "data": { "id": <run id>, "status": "queued" } }. Then poll GET /v1/scraper/runs/{id} until succeeded and fetch records via GET /v1/scraper/runs/{id}/records.

💡 You can also use deliveryMode: "sync" (small jobs block until terminal, auto fallback to polling on timeout) — see quick-start · Sync mode.

Endpoints:

Profile

Extract a profile's public information by URL (including work experience, education, and skills). Each URL is one target; submit multiple in a single run for batching.

Endpoint: POST /v1/scraper/linkedin/profile

Target fields (each targets[] element):

Output fields (each record):

Submit example (one run scraping 2 profiles):

curl -X POST "https://api.antsdata.com/v1/scraper/linkedin/profile" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      { "profileUrl": "https://www.linkedin.com/in/williamhgates/" },
      { "profileUrl": "https://www.linkedin.com/in/satyanadella/" }
    ]
  }'

Returns 201 → { "code": 0, "data": { "id": 1287345, "status": "queued" } }. Record the id, poll GET /v1/scraper/runs/1287345 until succeeded, then fetch records.

Company

Extract a company page's public information by URL. Each URL is one target; submit multiple in a single run for batching.

Endpoint: POST /v1/scraper/linkedin/company

Target fields (each targets[] element):

Output fields (each record):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/linkedin/company" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      { "companyUrl": "https://www.linkedin.com/company/microsoft/" }
    ]
  }'

Returns 201 → { "code": 0, "data": { "id": 1287346, "status": "queued" } }. Poll that id until succeeded, then fetch records.

Jobs

Search job listings by keywords, location, experience level, and more. One search condition is one target.

Endpoint: POST /v1/scraper/linkedin/jobs

Target fields (each targets[] element):

Output fields (each record):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/linkedin/jobs" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      {
        "keywords": "data engineer",
        "location": "United States",
        "resultsLimit": 100,
        "experienceLevel": "MID_SENIOR",
        "jobType": "FULL_TIME",
        "workplaceType": "REMOTE"
      }
    ]
  }'

Returns 201 → { "code": 0, "data": { "id": 1287347, "status": "queued" } }. Poll that id until succeeded, then page through the job list.

Profile Posts

Extract posts published by a person. At least one of profileUrls / companyUrls must be non-empty.

Endpoint: POST /v1/scraper/linkedin/posts

Target fields (each targets[] element):

Output fields (each record):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/linkedin/posts" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      {
        "profileUrls": ["https://www.linkedin.com/in/williamhgates/"],
        "resultsLimit": 25,
        "includeComments": false
      }
    ]
  }'

Returns 201 → { "code": 0, "data": { "id": 1287348, "status": "queued" } }. Poll that id until succeeded, then fetch post records.

Company Posts

Extract posts published by a company page, using the company page URL as the main entry. At least one of companyUrls / profileUrls must be non-empty.

Endpoint: POST /v1/scraper/linkedin/posts-company

Target fields (each targets[] element):

Output fields (each record, same as Profile Posts):

Submit example:

curl -X POST "https://api.antsdata.com/v1/scraper/linkedin/posts-company" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "deliveryMode": "async",
    "recordLimit": 1000,
    "targets": [
      {
        "companyUrls": ["https://www.linkedin.com/company/microsoft/"],
        "resultsLimit": 25,
        "includeComments": false
      }
    ]
  }'

Returns 201 → { "code": 0, "data": { "id": 1287349, "status": "queued" } }. Poll that id until succeeded, then fetch post records.

Fetching Data & Polling

After submitting, every endpoint follows the same run lifecycle to retrieve data:

1. Poll GET /v1/scraper/runs/{id} (back off 1s→2s→5s) until succeeded / failed (terminal).
2. Page through records via GET /v1/scraper/runs/{id}/records?page=1&pageSize=20; items[] matches the "Output fields" above.
3. Or download the full result via GET /v1/scraper/runs/{id}/download?format=csv.

An end-to-end example (Python submit / poll / fetch) is in Quick Start; the envelope, state machine, billing, and error codes are in Auth & Error Handling.

FAQ

Q: Does the call return data directly?

No. Scraping is asynchronous: submit to get a run id, poll until succeeded, then fetch records by id.

Q: Can I scrape multiple profiles / companies in one run?

Yes. For Profile / Company, each URL is one target, and a single run can hold multiple targets; per-target success or failure is in the run object's tasks[] (see Auth & Error Handling).

Q: Which endpoint should I use for profile vs company posts?

Use /posts (main entry profileUrls) for personal profile posts; use /posts-company (main entry companyUrls) for company page posts. Both endpoints share the same output fields.

Q: Do I need to log into the target account?

No. Only public data is extracted; private accounts cannot be scraped.

Next Steps

• Platform guides: TikTok · X · Instagram · Facebook · Google · YouTube · Amazon
• Synchronous search: Google SERP
• Auth & Error Handling — Unified envelope, run state machine, billing & error codes