LinkedIn Profile Scraper - No Login, JSON & CSV

Use profiles or the documented username/legacy URL inputs. Start with maxProfiles and keep useUpstreamFallback false unless you explicitly want separately billed fallback requests.

{
  "profiles": [
    "https://www.linkedin.com/in/whoareyouanas/",
    "neal-mohan"
  ],
  "maxProfiles": 5,
  "includeEmail": false,
  "useUpstreamFallback": false
}

• Success and partial records are usable dataset items; partial can mean only a name and headline are available.
• Failed targets are documented in DIAGNOSTICS outside the billed dataset. Preserve status, error, and scraped_at in downstream workflows.

{
  "input": "example-person",
  "basic_info": {
    "fullname": "Example Person",
    "headline": "Software Engineer",
    "profile_url": "https://linkedin.com/in/example-person",
    "public_identifier": "example-person",
    "current_company": "Example Company",
    "location": {
      "country": "",
      "city": "",
      "full": "",
      "postal_code": "",
      "country_code": ""
    },
    "top_skills": [
      "TypeScript"
    ],
    "email": null
  },
  "experience": [],
  "education": [],
  "certifications": [],
  "languages": [],
  "status": "partial",
  "error": null,
  "scraped_at": "2026-09-12T00:00:00.000Z"
}

Fields in the documented output view

Output views select columns. They do not necessarily filter record types or exhaust the full JSON payload. Use structured JSON when you need nested arrays or objects.

These are the active public event prices checked on 2026-10-29, in USD. They describe each event, not a universal flat price for a run. Confirm your current Apify plan and run budget before starting.

A result limit and a spending cap are different controls. Account charges, applicable taxes, and separately billed providers or proxies must be considered where relevant. A cap setting is not a minimum invoice charge.

Test a small run in Apify Console, inspect its records and charges, then save a task or call the actor from your own application. Keep your Apify token in an environment variable. Source-specific credentials, if required, are separate from the Apify API token.

# Save the input example as input.json and set APIFY_TOKEN.
# This request starts an asynchronous, potentially billable run.
curl --request POST \
  'https://api.apify.com/v2/acts/whoareyouanas~linkedin-profile-actor/runs' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data @input.json

The response identifies the run. Wait for it to finish, inspect its status, and use its default dataset and key-value store to retrieve results. A successful run can still contain partial or failed records; check the output contract above before continuing downstream.