Linkedin Open Profile Status

Linkedin Open Profile Status

Linkedin Open Profile Status is an Apify actor that checks whether a LinkedIn profile displays the “Open to work” signal quickly and at scale. It solves the tedious problem of manually visiting profiles to verify job-seeking badges by automating detection through fast HTTP parsing and robust browser checks. Built for marketers, developers, data analysts, and researchers, it helps you enrich outreach and talent workflows while addressing queries around LinkedIn Open Profile meaning and LinkedIn Open Profile vs Open to Work. Run it in bulk and plug the results straight into your automations. 🚀

What data / output can you get?

Below are the exact fields the actor produces in its dataset and key-value store outputs. Values reflect real behavior from the code.

Data field	Description	Example value
url	The LinkedIn profile URL that was processed	https://www.linkedin.com/in/ajjames
open_to_work	Final detection result; true/false, or null if unknown	true
message	Status message for the record	ok
proxy_mode	Which proxy mode processed the URL	direct
data.open_to_work	Nested result object for compatibility	true
debug.proxy_mode	Debugging info for the run	direct
debug.details	Extra context like ok, no_signal, status=403, goto_timeout	ok
OUTPUT.data.open_to_work	Key-value store (single-input) result	false
OUTPUT.message	Key-value store status message	ok
OUTPUT[].url	Key-value store (bulk) record URL	https://www.linkedin.com/in/ajjames
OUTPUT[].data.open_to_work	Key-value store (bulk) nested result	false
OUTPUT[].message	Key-value store (bulk) status	ok

Notes:

• Results are streamed live to the default dataset as each profile finishes, so you can watch rows appear in real time.
• You can export the dataset to CSV, JSON, or Excel directly from Apify.

Key features

• ⚡ Dual detection engine (fast + robust) Uses HTTP + HTML signal extraction first, then falls back to Playwright badge detection when needed for accuracy.

• 🪜 Adaptive proxy ladder with stickiness Starts DIRECT (no proxy). If blocked → Datacenter proxy. If blocked → Residential proxy with up to 3 retries. After the first DIRECT block, all remaining requests stick to Residential for reliability.

• 📦 Bulk-friendly processing Supply multiple profile URLs and process them in one run; results are pushed as each item completes for fast feedback loops.

• 🔐 Optional authentication for reliability Provide your LinkedIn li_at cookie to reduce blocks and improve consistency; the value is handled as a secret input.

• 📡 Live dataset streaming Results are saved to the dataset in real time, with detailed logs of proxy events, blocks, retries, and outcomes.

• 👨‍💻 Developer-ready Trigger via the Apify API/SDK, read structured JSON, and connect to downstream systems for lead scoring, routing, and enrichment.

• 🛡️ Production-minded resilience Clear block detection, retries on Residential proxies, and debug fields to troubleshoot edge cases with confidence.

How to use Linkedin Open Profile Status - step by step

1. Create or sign in to your Apify account.
2. Open the “Linkedin Open Profile Status” actor on Apify.
3. Add input data:
   • Paste one or more LinkedIn profile URLs into “Profile URLs (bulk)” (e.g., https://www.linkedin.com/in/ajjames).
4. (Optional) Add your LinkedIn li_at cookie to improve reliability and reduce blocks.
5. (Optional) Review Proxy configuration:
   • Default is DIRECT (no proxy). The actor automatically falls back only if blocked.
6. Start the run. Watch logs for strategy and proxy ladder events; the dataset table fills in real time.
7. Download results from the dataset in your preferred format (CSV, JSON, Excel).
8. Pro Tip: Use the Apify API to integrate results into CRM or enrichment pipelines; the actor writes a stable OUTPUT record in the key-value store for each run.

Use cases

Use case name	Description
Recruiting pipelines — candidate status enrichment	Identify whether profiles display the Open to work badge and route prospects accordingly.
Marketing & outreach — lead filtering	Prioritize segments where job-seeking signals may influence messaging and conversion paths.
Data enrichment for CRM	Append open_to_work signals to profiles in your CRM to power custom scoring and routing logic.
Research & analytics — labor market signals	Analyze cohorts for Open to work prevalence by function, location, or seniority.
Product & ops — QA for profile datasets	Validate large lists of LinkedIn URLs for the presence/absence of Open to work to keep datasets fresh.
API pipelines — automation-first workflows	Orchestrate at scale via the Apify API/SDK; consume structured JSON for downstream ETL.

Why choose Linkedin Open Profile Status?

A precise, automation-ready detector purpose-built for “Open to work” signals on LinkedIn.

• 🎯 Accurate detection paths: Combines HTML parsing with Playwright badge checks to balance speed and robustness.
• 🔁 Smart proxy strategy: DIRECT → Datacenter → Residential (×3), then stick to Residential after the first DIRECT block for stability.
• 🧩 Structured results: Clear JSON schema with top-level and nested data for flexible downstream use.
• 🧪 Debug-first design: Debug fields (proxy mode, details) help diagnose blocks, timeouts, and no-signal cases.
• 👨‍💻 Developer access: Works seamlessly with the Apify API and SDKs for integration into automation pipelines.
• 🧭 Ethical-by-design: Intended for publicly available pages; optional authentication via li_at is supported to reduce blocks.
• 💸 Cost-aware alternative: More reliable than brittle extensions or one-off scripts, with production-minded retries and fallbacks.

In short: a focused detector that outperforms unstable browser add-ons and ad‑hoc scripts by offering consistency, observability, and integration-ready output.

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

Yes — when used responsibly. The actor is designed for publicly available LinkedIn pages and adds optional authentication only if you provide a li_at cookie. Always ensure:

• You access data in line with LinkedIn’s Terms of Service.
• You comply with regulations like GDPR/CCPA where applicable.
• You avoid misuse (e.g., spam) and respect user privacy and platform policies.
• If you provide li_at, the actor accesses pages as permitted by your authenticated session.

For edge cases or regulated workflows, consult your legal team.

Input parameters & output format

Example input (UI / API):

{
  "startUrls": [
    "https://www.linkedin.com/in/ajjames"
  ],
  "liAtCookie": "LIAT_COOKIE_VALUE",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Parameters (from schema):

• startUrls (array)
  • Description: Add one or more LinkedIn profile URLs.
  • Default: None
  • Required: Yes
• liAtCookie (string)
  • Description: Optional LinkedIn authentication cookie value. Recommended to reduce blocks and improve reliability. Stored as a secret input.
  • Default: null
  • Required: No
• proxyConfiguration (object)
  • Description: Default is DIRECT (no proxy). The actor will automatically fall back to Apify Proxy only when blocked.
  • Default: DIRECT (no proxy)
  • Required: No

Output examples:

• Dataset item (per profile):

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

• Key-value store OUTPUT (single input):

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

• Key-value store OUTPUT (multiple inputs):

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

Notes:

• open_to_work may be null when the actor cannot obtain a definitive signal (e.g., timeouts, atypical page structure, or persistent blocks).
• message and debug.details provide useful context for handling edge cases programmatically.

FAQ

What does “Open Profile” mean on LinkedIn, and does this actor check it?

Open Profile is a LinkedIn Premium feature that lets others message you for free without InMail credits. This actor does not check Open Profile; it detects the “Open to work” badge on LinkedIn profiles. See “LinkedIn Open Profile vs Open to Work” differences when planning your workflow.

How do I turn on LinkedIn Open Profile status?

You can manage this in your LinkedIn settings if you have the relevant Premium option. Because Open Profile is separate from the “Open to work” badge, enabling it does not affect this actor’s results.

Can this actor check if someone has LinkedIn Open Profile?

No. It checks for the “Open to work” badge. If you need to identify whether users allow messages from anyone (Open Profile), that is a different signal than the open_to_work field returned here.

Do I need to log in or provide a cookie?

No. The actor works without login. However, adding your li_at cookie is recommended to reduce blocks and improve reliability, especially at scale.

What proxies does it use and when?

It starts DIRECT (no proxy). If blocked, it tries a Datacenter proxy; if still blocked, it switches to Residential proxies and retries up to 3 times. After the first DIRECT block, the actor sticks to Residential proxies for all remaining requests.

What does open_to_work = null mean in the output?

It means the actor could not definitively determine the badge status for that URL (e.g., due to timeouts, blocks, or missing signals). Use message and debug.details to diagnose the cause (e.g., no_signal, status=403, goto_timeout).

Can I message anyone on LinkedIn without InMail using “Open to work”?

No. “Open to work” indicates job-seeking status. Messaging anyone without InMail is related to LinkedIn’s Open Profile Premium feature or other allowances, not the Open to work badge.

How can I export and integrate the results?

All items land in the Apify dataset, which you can export as CSV, JSON, or Excel. You can also retrieve results programmatically via the Apify API for pipelines with Zapier, Make, n8n, or custom scripts.

Is this actor suitable for bulk runs and automation?

Yes. It’s designed for multi-URL processing with live dataset writes and a structured JSON output that fits API-driven enrichment and analytics workflows.

Closing CTA / Final thoughts

Linkedin Open Profile Status is built to detect the “Open to work” signal on LinkedIn profiles with speed, resilience, and integration-ready output. By combining fast HTML parsing with Playwright-based checks and an adaptive proxy ladder, it delivers reliable results for recruiters, marketers, analysts, and developers. Use the dataset exports for spreadsheets and dashboards, or wire it into your API pipelines for automated enrichment. Start extracting smarter signals from LinkedIn profiles and streamline your outreach and research workflows today.