# Linkedin Open Profile Status (`scraperoka/linkedin-open-profile-status`) Actor 🔍 Open Profile Status: I’m available to connect and explore opportunities in B2B research, sales & recruitment. 🚀 Share your goals—let’s connect and collaborate. ✅ Fast, reliable, and detail-focused. - **URL**: https://apify.com/scraperoka/linkedin-open-profile-status.md - **Developed by:** [Scraperoka](https://apify.com/scraperoka) (community) - **Categories:** Jobs, Lead generation, Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.01 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### LinkedIn Open Profile Status 🔍 **LinkedIn Open Profile Status** analyzes LinkedIn profile HTML to detect whether a profile is set to “Open Profile” (the open profile status meaning). It helps you verify LinkedIn profile visibility status and determine if someone may accept messages for free—useful for lead prospecting, recruiting outreach, and compliance-friendly research into LinkedIn open profile privacy settings. Whether you’re a marketer, recruiter, or data analyst, this actor automates the “is this profile open to messages?” check at scale, saving you hours of manual work when working with LinkedIn open profile status meaning and LinkedIn profile open to recruiters workflows. --- ### 🚀 Why choose LinkedIn Open Profile Status? | Feature | Benefit | | --- | --- | | ✅ **Open Profile detection from profile HTML** | Quickly determine LinkedIn open profile status without manual inspection | | ✅ **Structured JSON results per profile** | Feed results directly into spreadsheets, CRMs, and analysis pipelines | | ✅ **Built-in resilience for inconsistent access** | Detects authwall situations and continues processing other profiles | | ✅ **Confidence scoring + reason** | Understand whether the LinkedIn profile open profile option was detected with high or low confidence | | ✅ **Scales to multiple profile URLs per run** | Process LinkedIn profile visibility setting checks in batches efficiently | | ✅ **Dataset output for easy export** | Collect results in an Apify dataset for JSON/CSV export | --- ### 🔑 Key features - 🔍 **Open Profile status detection:** Detects “Open Profile” indicators in the fetched profile content (including high-confidence signals). - 🧠 **Confidence-aware output:** Returns a result with confidence level (“high”, “medium”, or “low”) and a human-readable reason. - 🛡️ **Authwall handling:** If an authwall is detected, the actor flags it and sets the open profile result accordingly. - 📥 **Accepts one URL per item (batch-friendly):** You can analyze multiple LinkedIn profile links in a single run. - 📊 **Clear, minimal dataset fields:** Outputs a compact JSON object with `open_profile` and a run `message` for each profile. - 💾 **Real-time dataset saving:** Each profile’s result is pushed to the Apify dataset as it’s processed. --- ### 📝 Input Provide input via an `input.json` file. Example structure: ```json { "linkedin_url": "https://www.linkedin.com/in/ajjames" } ```` #### Input Fields | Field | Required | Description | | --- | --- | --- | | `linkedin_url` | Yes | LinkedIn profile URL to analyze (for example, `https://www.linkedin.com/in/ajjames`). | > Note: The actor code also checks for additional fields like `linkedin_urls`, but the documented input schema includes only `linkedin_url`. To avoid errors, pass at least `linkedin_url`. *** ### 📦 Output The actor saves each profile’s data in JSON format to the default Apify dataset view (“Scraped Profiles”). Each dataset row contains an object with a `data` object and a `message` string. Example output item: ```json { "data": { "open_profile": true }, "message": "ok" } ``` #### Output Fields | Field | Type | Description | | --- | --- | --- | | `data.open_profile` | boolean or null | Whether the actor detected “Open Profile” status. Set to `null` when authwall is detected or analysis can’t confirm it. | | `message` | string | A status message for the run item (for example, `ok`, `authwall detected`, or `error: ...`). | *** ### 🧭 How to use LinkedIn Open Profile Status (via Apify Console) 1. **Open Apify Console**\ Log in at https://console.apify.com and go to the **Actors** tab. 2. **Find the actor**\ Search for **LinkedIn Open Profile Status** and open its actor page. 3. **Configure the INPUT**\ In the **INPUT** section, enter your LinkedIn profile URL in the `linkedin_url` field (e.g. `https://www.linkedin.com/in/ajjames`). 4. **Run the actor**\ Click **Run** to start the job. You’ll see logs while it processes the provided profile. 5. **Watch progress in logs**\ The actor logs each profile being processed and records whether it detected an Open Profile status or encountered an authwall. 6. **Open the OUTPUT dataset**\ After the run completes, open the **OUTPUT** tab and view the dataset named **LinkedIn Open Profile Data** (default view: “Scraped Profiles”). 7. **Export your results**\ Export the dataset to **JSON** or **CSV** using Apify’s dataset export options. No coding required — get LinkedIn open profile status checks in minutes. *** ### ⚙️ Advanced features & SEO optimization - 📌 **Optimized for LinkedIn Open Profile Status detection:** Engineered specifically to excel at LinkedIn open profile status, including LinkedIn open to work status style outreach validation use cases. - 🧪 **Confidence-driven interpretation:** Outputs meaningful detection signals (“high”, “medium”, or “low” internally with a reason) to help interpret LinkedIn profile visibility status results. - 🌐 **Works with public web profile HTML:** Designed to analyze profile HTML content and determine LinkedIn profile open profile privacy-related visibility signals. - 🔄 **Resilient processing flow:** Includes detection for authwall situations and structured handling so you can run batches reliably. - 🧾 **Dataset-first output:** The results are saved item-by-item to make it easy to continue downstream work (for example, enrichment and segmentation). *** ### 🎯 Best use cases - 📈 **Lead gen teams checking message eligibility:** Validate LinkedIn open profile status meaning to prioritize outreach to profiles most likely to accept messages for free. - 🧑‍💼 **Recruiters sourcing candidates:** Assess LinkedIn profile open to recruiters readiness when searching talent using LinkedIn open profile privacy settings context. - 🕵️ **Market researchers mapping public visibility signals:** Study LinkedIn profile visibility setting patterns across segments using LinkedIn profile visibility status. - ✉️ **Cold outreach ops optimizing targeting rules:** Reduce wasted campaigns by screening for LinkedIn open profile option indicators before adding prospects. - 📊 **Data analysts building prospect datasets:** Combine Open Profile status results into analysis tables for “visible to everyone” style segmentation. - 💻 **Automation pipelines for B2B enrichment:** Turn LinkedIn open profile activity status checks into structured dataset rows for CRM ingestion and reporting. *** ### 🧰 Technical specifications - **Supported Input Formats** - ✅ `linkedin_url` as a single LinkedIn profile URL string - **Proxy Support** - ✅ Built-in proxy support for reliable scraping (configurable behavior in the actor environment) - **Retry Mechanism** - ✅ Includes resilience logic to handle inconsistent access scenarios (e.g., authwall detection) - **Dataset Structure** - ✅ Each dataset item contains: - `data.open_profile` - `message` - **Rate Limits & Performance** - ⚠️ Performance depends on profile accessibility; the actor processes profiles sequentially and saves results as it goes. - **Limitations** - ❌ Private/restricted profiles may not yield a confirmed result - ❌ Authwall situations result in `open_profile: null` *** ### ❓ FAQ #### Does LinkedIn Open Profile Status require login? ❌ No login credentials are provided through the input. The actor fetches the profile content and may report `authwall detected` in the `message` if access is restricted. #### What does “open\_profile” mean in the output? ✅ `open_profile` indicates whether the actor detected “Open Profile” status in the profile HTML. If it can’t confirm due to an authwall, it returns `null`. #### How can I use this for LinkedIn open profile privacy settings checks? ✅ Use the `open_profile` boolean (or `null` when blocked) as a practical proxy for whether the profile appears to allow free messaging—helpful when assessing LinkedIn open profile privacy settings and LinkedIn profile visibility status. #### Will it work for multiple profiles in one run? ✅ The actor is designed to process profile URLs in a batch-style loop internally. The input schema explicitly requires `linkedin_url`, and you can run multiple profiles by running the actor repeatedly or by extending your job inputs as supported in your environment. #### Can I integrate the results into a CRM or data warehouse? ✅ Yes. The actor outputs structured JSON dataset items with `data.open_profile` and `message`, which are easy to export and ingest for segmentation and enrichment workflows. #### What if the actor can’t detect Open Profile status? ✅ You’ll receive a `message` indicating whether an error occurred or whether an authwall was detected. In those cases, `open_profile` may be `null`. #### Does this actor “scrape private profile information”? ❌ No. This actor analyzes publicly accessible profile HTML. It does not access password-protected or private profile data. *** ### 🤝 Support & feature requests If you want to improve LinkedIn Open Profile Status (for example, better handling for edge cases related to LinkedIn open profile not showing, or enhanced output fields), share your ideas with us. - 💡 **Feature Requests:** Request enhancements like additional dataset fields or improved interpretation for edge cases. - 📧 **Contact:** Email . Your feedback helps shape the roadmap for LinkedIn open profile status detection. *** ### 🏁 Closing CTA / Final thoughts *Run LinkedIn Open Profile Status when you need a fast, structured way to verify LinkedIn open profile status and prioritize outreach at scale.* With this SEO-optimized **LinkedIn Open Profile Status** actor, you can turn profile visibility checks into actionable datasets quickly. *** ### Disclaimer **This tool only accesses publicly accessible sources.** It does not access private profiles or password-protected data. It’s your responsibility to comply with applicable laws (including GDPR/CCPA where relevant), spam regulations, and the platform’s terms of service when collecting and using any data. For data removal requests, contact . # Actor input Schema ## `linkedin_url` (type: `string`): LinkedIn profile URL to analyze ## Actor input object example ```json { "linkedin_url": "https://www.linkedin.com/in/ajjames" } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "linkedin_url": "https://www.linkedin.com/in/ajjames" }; // Run the Actor and wait for it to finish const run = await client.actor("scraperoka/linkedin-open-profile-status").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "linkedin_url": "https://www.linkedin.com/in/ajjames" } # Run the Actor and wait for it to finish run = client.actor("scraperoka/linkedin-open-profile-status").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "linkedin_url": "https://www.linkedin.com/in/ajjames" }' | apify call scraperoka/linkedin-open-profile-status --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/linkedin-open-profile-status", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Linkedin Open Profile Status", "description": "🔍 Open Profile Status: I’m available to connect and explore opportunities in B2B research, sales & recruitment. 🚀 Share your goals—let’s connect and collaborate. ✅ Fast, reliable, and detail-focused.", "version": "1.0", "x-build-id": "Kui1am2aRfF8iuX83" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~linkedin-open-profile-status/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-linkedin-open-profile-status", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scraperoka~linkedin-open-profile-status/runs": { "post": { "operationId": "runs-sync-scraperoka-linkedin-open-profile-status", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scraperoka~linkedin-open-profile-status/run-sync": { "post": { "operationId": "run-sync-scraperoka-linkedin-open-profile-status", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "linkedin_url" ], "properties": { "linkedin_url": { "title": "LinkedIn URL", "type": "string", "description": "LinkedIn profile URL to analyze" } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```