Nimbryxo Studio

Use LinkedIn Public Profile Credentials & Company Lookup with Python

Look up public LinkedIn profiles by URL or username and get work history, education, certifications, honors, volunteer work, and projects, with the current employer's own company page details attached. No login or cookies needed.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "enrichCompany": false,
  "maxPosts": 3,
  "pacing": "balanced",
  "profileUrls": [
    "https://www.linkedin.com/in/williamhgates"
  ],
  "useUnblocker": true
}

Download input.example.json and save your reviewed copy as input.json.

FieldTypeRequiredDescription
profileUrlsarrayrequiredLinkedIn profile URLs (https://www.linkedin.com/in/username) or bare usernames. Public profiles work best; normal profiles may require the anti-bot fallback.
enrichCompanybooleanoptionalFetch the current employer's public LinkedIn company page for extra detail (followers, offices, affiliated pages, similar pages, updates, founded, tagline, size, industry, website, headquarters, logo). Adds one request per unique company and is cached within the run.
maxPostsintegeroptionalMaximum number of recent public posts to include per profile. Set 0 to skip posts.
pacingstringoptionalHow long to wait between profiles. Use a slower pacing for large runs if LinkedIn starts refusing requests.
useUnblockerbooleanoptionalAllow the final anti-bot fallback after LinkedIn returns a real block (999/403 or a sign-up wall). Profiles that load directly never use it.
proxyConfigurationobjectoptionalOptional Apify proxy used as a middle rung before the anti-bot fallback. Leave empty to go straight from a direct request to the fallback only when blocked.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/c5Y5dfWU8TAiArwdP/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

One row per input: public profile identity, experience, education, skills, languages, credentials, publications, recommendations, posts, current-company intelligence, data-quality flags, or a truthful error row.

Questions before you run

Which inputs are required?

The published required fields are profileUrls

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Generated from source build 6nFhX9k4gxV44tkTO and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.