Linkedin Open Profile Status

Linkedin Open Profile Status

Linkedin Open Profile Status is a focused LinkedIn “Open to work” status checker that detects whether a profile displays the Open to work badge — fast, reliable, and built for bulk enrichment. It helps teams avoid confusion around LinkedIn Open Profile status vs InMail by zeroing in on the Open to work signal for clean lead qualification. Ideal for sales, recruiters, data analysts, and developers, it blends fast HTTP extraction with Playwright verification and an automatic proxy ladder to keep results flowing at scale.

What data / output can you get?

You’ll receive one structured record per profile pushed live to the dataset while the run is in progress.

Data type	Description	Example value
url	The LinkedIn profile URL processed	https://www.linkedin.com/in/ajjames
open_to_work	Top-level boolean flag inferred from the page	true
proxy_mode	Connection mode used for the successful detection or last attempt	"direct"
message	Status message describing the result	"ok"
data	Envelope object mirroring the core flag	{"open_to_work": true}
data.open_to_work	The Open to work flag inside the data object	true
debug	Diagnostic info (when available)	{"proxy_mode": "direct", "details": "ok"}
debug.proxy_mode	Proxy mode used during detection	"residential"
debug.details	Extra details from the last strategy (when present)	"ok", "goto_timeout", "status=429"

Notes:

• When signals are inconclusive or requests are blocked, open_to_work may be null and message will explain the last known state (for example, “Failed to fetch profile. Last=playwright:goto_timeout”).
• Export results from the dataset in common formats such as JSON, CSV, or Excel.

Key features

• ⚡ Fast, dual-layer detection
  Lightweight HTML signal extraction backed by a Playwright badge check for resilient, accurate detection of the “Open to work” indicator.

• 🪜 Automatic proxy ladder with stickiness
  Starts DIRECT (no proxy), falls back to Datacenter if blocked, then Residential with up to 3 retries. After the first DIRECT block, remaining requests stick to Residential for stability.

• 📦 Bulk-ready inputs
  Paste multiple profile URLs via startUrls. In advanced JSON, you can also pass urls and keywords for flexible batching.

• 🔐 Optional cookie for fewer blocks
  Provide liAtCookie to reduce blocks and improve reliability. It’s handled as a secret input.

• 📈 Live, streaming dataset writes
  Each profile result is pushed to the dataset in real time — watch rows appear as the run progresses.

• 👩‍💻 Developer-friendly & automation-ready
  Run on Apify, call via API, or plug into Python/JS workflows. Chain runs in Make, n8n, or Zapier for enrichment pipelines.

• 🛡️ Production-minded reliability
  Clear logs on proxy events, blocks, and retries; anti-blocking delays; and session stickiness for stable batch execution.

How to use Linkedin Open Profile Status - step by step

1. Sign in to Apify and open the Linkedin Open Profile Status actor.
2. Add input data: paste one or more LinkedIn profile URLs into startUrls.
3. (Optional, advanced JSON) Provide additional urls or keywords — keywords like a public identifier will be normalized into profile URLs.
4. (Optional) Add liAtCookie to reduce blocking. You can run without it, but adding it improves reliability.
5. Leave Proxy configuration at default (DIRECT). The actor automatically escalates proxies only if blocked.
6. Click Start. The actor tries fast HTTP extraction first, then uses Playwright if needed.
7. Monitor progress in the logs and see dataset rows appear live.
8. Export results from the dataset in JSON/CSV/Excel or pull them via the Apify API.

Pro tip: For larger batches, combine startUrls with urls and keywords in advanced JSON input and schedule runs via the Apify API for ongoing enrichment.

Use cases

Use case	Description
Sales ops lead triage	Prioritize outreach by flagging profiles that show “Open to work” and route them to reps automatically.
Recruiting pipelines	Surface candidates who display “Open to work” and feed them into sourcing workflows.
CRM/data enrichment	Append open_to_work flags to contact records for segmentation and campaign logic.
Market research	Quantify “Open to work” signals across cohorts for talent and hiring trend analysis.
API-driven pipelines	Trigger checks programmatically and stream results into data lakes or dashboards.
Academic studies	Measure prevalence of “Open to work” across roles, industries, or geographies in bulk.

Why choose Linkedin Open Profile Status?

A precision-first, reliable detector for the LinkedIn “Open to work” signal — built for automation and scale.

• ✅ Accuracy-first pipeline: Fast HTML signals backed by Playwright badge verification.
• 🌍 Resilient at scale: Automatic proxy escalation with Residential stickiness after the first DIRECT block.
• 🧩 Developer access: Works on the Apify platform with API integration for programmatic runs.
• 🛡️ Safer than extensions: Server-side execution with clear logs — no brittle browser add-ons.
• 💰 Cost-aware throughput: HTTP-first approach minimizes heavy browser usage when not needed.
• 🔧 Flexible inputs: startUrls in UI; plus urls, keywords, and timeouts in advanced JSON for power users.
• 🔄 Export anywhere: Download from datasets or connect via API to analytics and CRM tools.

Bottom line: a focused “Open to work” checker that outperforms ad‑hoc scripts and unstable tools with production-ready reliability.

Is it legal / ethical to use Linkedin Open Profile Status?

Yes — when used responsibly. This actor reads publicly accessible LinkedIn profile content and can run without login; liAtCookie is optional and only reduces blocking.

Guidelines:

• Only use data from publicly visible profile content.
• Comply with applicable regulations (e.g., GDPR, CCPA) and LinkedIn’s terms.
• Do not collect or use data for spam or abusive activities.
• Consult your legal team for edge cases and specific compliance requirements.

This tool does not change LinkedIn settings (for example, it does not enable/disable LinkedIn Open Profile settings) and does not verify free messaging availability. It focuses solely on detecting the “Open to work” badge.

Input parameters & output format

Example JSON input (advanced):

{
  "startUrls": [
    "https://www.linkedin.com/in/ajjames"
  ],
  "urls": [
    "https://www.linkedin.com/in/exampleuser"
  ],
  "keywords": [
    "public-identifier-slug"
  ],
  "liAtCookie": "YOUR_LI_AT_COOKIE",
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxConcurrency": 1,
  "pageTimeoutSeconds": 60
}

Schema parameters (UI fields):

• startUrls (array) — Add one or more LinkedIn profile URLs. Example: https://www.linkedin.com/in/ajjames. Default: not set. Required: Yes.
• liAtCookie (string, nullable) — Optional LinkedIn authentication cookie value. Recommended to reduce blocks and improve reliability. Stored as a secret input. Default: not set. Required: No.
• proxyConfiguration (object) — Default is DIRECT (no proxy). The Actor will automatically fall back to Apify Proxy only when blocked. Default: DIRECT (no proxy). Required: No.

Advanced (JSON-only, supported by the actor code):

• urls (array): Additional profile URLs to process.
• keywords (array): Public identifiers that are normalized into profile URLs.
• maxConcurrency (number): Limits parallel processing.
• pageTimeoutSeconds (number): Playwright page timeout in seconds.

Dataset row example:

{
  "url": "https://www.linkedin.com/in/ajjames",
  "open_to_work": true,
  "proxy_mode": "residential",
  "data": {
    "open_to_work": true
  },
  "message": "ok",
  "debug": {
    "proxy_mode": "residential",
    "details": "ok"
  }
}

Key-value store OUTPUT examples:

• Single profile:

{
  "data": { "open_to_work": false },
  "message": "ok"
}

• Multiple profiles:

[
  {
    "url": "https://www.linkedin.com/in/exampleuser",
    "data": { "open_to_work": null },
    "message": "Failed to fetch profile. Last=playwright:goto_timeout"
  },
  {
    "url": "https://www.linkedin.com/in/ajjames",
    "data": { "open_to_work": true },
    "message": "ok"
  }
]

Note: open_to_work may be null when no definitive signal is detected or when requests are blocked.

FAQ

Does this actor check “Open Profile” messaging or only “Open to work”?

✅ It detects “Open to work” only. If you’re comparing LinkedIn Open Profile vs InMail or wondering about free messages, this actor does not verify Open Profile messaging availability. It focuses on the Open to work badge.

Do I need to log in or use cookies?

ℹ️ No, login is not required. You can run without cookies. Providing liAtCookie is optional but recommended to reduce blocks and improve reliability.

Can I run it in bulk?

🚀 Yes. Add multiple URLs via startUrls. In advanced JSON input, you can also provide urls and keywords to expand your batch.

How does the proxy fallback work?

🛡️ The run starts DIRECT (no proxy). If blocked, it falls back to Datacenter; if still blocked, it uses Residential and retries up to 3 times. After the first DIRECT block, remaining requests stick to Residential for stability.

What’s included in the output data?

📦 Each dataset item includes url, open_to_work, proxy_mode, message, a data object with open_to_work, and a debug object with proxy_mode and (when available) details.

How can I export results?

📤 Results stream to the default dataset in real time and can be exported in JSON, CSV, or Excel, or fetched via the Apify API for downstream tools like CRMs and dashboards.

Why is open_to_work sometimes null?

ℹ️ If the badge isn’t visible, signals are inconclusive, or the request is blocked, open_to_work may be null. The message field will indicate what happened (for example, timeout or last status).

Can I use this to check if someone has LinkedIn Open Profile enabled?

🔎 Not directly. This actor does not check LinkedIn Open Profile contact options or free messaging. It only detects the “Open to work” badge.

How to enable or disable LinkedIn Open Profile settings?

⚙️ This actor does not modify or read Open Profile settings. To manage Open Profile, use LinkedIn’s in‑product settings. This tool is designed strictly to detect the Open to work badge.

Is LinkedIn Premium Open Profile supported?

❌ No. The actor does not determine LinkedIn Premium Open Profile eligibility or status. It focuses solely on the Open to work indicator.

Final thoughts

Linkedin Open Profile Status is built to accurately detect the LinkedIn “Open to work” signal at scale. With fast HTTP checks, Playwright verification, and an automatic proxy ladder, it delivers reliable results for sales, recruiting, analytics, and research teams. Add your startUrls, optionally include liAtCookie for fewer blocks, and export clean open_to_work flags from the dataset. Developers can drive runs via the Apify API and plug outputs into automation pipelines. Start extracting smarter signals from LinkedIn profiles today.