# Linkedin Open To Work Status (`scrapedrift/linkedin-open-to-work-status`) Actor Extract LinkedIn Open To Work status from profiles at scale. Identify candidates actively seeking opportunities and collect profile details for recruitment, talent sourcing, lead generation, and hiring workflows. - **URL**: https://apify.com/scrapedrift/linkedin-open-to-work-status.md - **Developed by:** [ScrapeDrift](https://apify.com/scrapedrift) (community) - **Categories:** Lead generation, Jobs, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.99 / 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 To Work Status ⚡ — Detect the Open to Work badge from profile pages in bulk If you’re trying to understand a candidate’s LinkedIn Open to Work status, manually checking profiles one by one is slow and easy to get wrong. **LinkedIn Open To Work Status** scans the profiles you provide and flags whether “Open to work” appears on the page. It also helps with common questions like LinkedIn Open to Work not showing and LinkedIn Open to Work visibility. This is ideal for recruiters, outreach teams, and researchers who need quick, structured results across many profiles. In one run, you can validate Open to work status meaning for multiple LinkedIn profiles and get results immediately in your dataset. --- ### See the Data: Sample Output Here's a real record from a single run: ```json { "data": { "open_to_work": true }, "message": "ok" } ```` Here’s how errors look when a profile can’t be fetched: ```json { "data": { "open_to_work": false }, "message": "error: " } ``` And when an auth wall is detected, the actor returns: ```json { "data": { "open_to_work": false }, "message": "authwall detected (data might be incorrect)" } ``` | Field | Type | What It Tells You | |---|---|---| | `data.open_to_work` | boolean | Whether the profile page indicates LinkedIn Open to Work status | | `message` | string | A human-readable run status (e.g., `ok`, `authwall detected (data might be incorrect)`, or an error description) | | `status` | N/A | Not provided by this actor; use `message` to interpret outcomes | | `data` | object | The container for the extracted result(s) | | `data.open_to_work` | boolean | Main field you’ll filter on for LinkedIn Open to Work recruiter only style workflows | | `message` | string | Lets you track cases where LinkedIn Open to Work setting may be hidden behind access limits | | `data.open_to_work` | boolean | Default behavior on failures is `false` | | `message` | string | Useful for logging and auditing “LinkedIn Open to Work status meaning” checks | | `data` | object | Keep the shape stable when you load into Sheets/CRM | | `message` | string | Enables downstream logic for “Open to Work status LinkedIn” verification | Export your full dataset as JSON, CSV, or Excel from the Apify dashboard. *** ### Setting It Up Drop this into your `input.json` and you're ready to go: ```json { "startUrls": [ { "url": "https://www.linkedin.com/in/ajjames" } ] } ``` | Parameter | Required | What It Does | |---|---|---| | `startUrls` | ✅ | A list of LinkedIn profile URLs the actor should check for LinkedIn Open To Work status | *** ### What It Does This actor checks LinkedIn profile pages you provide and determines whether they show evidence of an “Open to work” state. #### Detects Open to work status on the profile page It evaluates the page content and determines whether the Open to work badge appears, helping you answer questions like LinkedIn Open to Work status meaning and whether LinkedIn Open to Work not showing might be due to missing on-page indicators. #### Fast bulk validation for LinkedIn Open to Work visibility By processing multiple LinkedIn profile URLs in a single run, you can validate LinkedIn Open To Work visibility across a list—without manually opening each profile. #### Clean, integration-ready output Results are pushed per profile with a consistent structure: `data.open_to_work` as a boolean and a `message` string that indicates whether the outcome is `ok`, blocked behind an auth wall, or an error occurred. #### Handles blocks and errors more gracefully If the actor encounters an authwall, it returns `message: "authwall detected (data might be incorrect)"`. If a fetch fails, it returns `data.open_to_work: false` along with an error message so you can see what needs re-checking. #### Built-in support for more reliable runs The actor includes proxy support options and uses resilient request logic, which helps when you’re checking many profiles—especially when LinkedIn Open to work location settings or visibility varies by account/page state. Overall, LinkedIn Open To Work Status gives you a practical way to check LinkedIn Open to work profile badge visibility at scale. *** ### Why LinkedIn Open To Work Status? There are plenty of ways to pull data from web profiles—here’s why LinkedIn Open To Work Status stands out. #### Clear yes/no signal for outreach workflows You get a straightforward `data.open_to_work` boolean plus a `message` field, so you can quickly separate profiles that show Open to work for jobs from those that don’t—without extra manual interpretation. #### Practical checks with resilience The actor includes retries and fallback handling, and it explicitly flags auth wall cases (with `authwall detected (data might be incorrect)`) so you can understand when LinkedIn Open to Work setting might not be fully observable. #### Easy-to-use input and predictable dataset output You provide `startUrls` and receive uniform records in the dataset, making it simple to run batches and compare outputs over time—useful when troubleshooting LinkedIn Open to Work not showing patterns. *** ### Real-World Use Cases **Recruitment Teams**\ A recruiter has a shortlist of candidates and wants to know who is actively signaling hiring intent. They feed the LinkedIn profile URLs into LinkedIn Open To Work Status and immediately get a boolean flag indicating whether the Open to work state appears on-page, speeding up shortlisting for outreach. This reduces time spent clicking through profiles and helps standardize checks related to LinkedIn hiring banner signals. **Sales Development Representatives**\ An SDR is building a list for targeted outbound and needs a quick filter before drafting messages. They run LinkedIn Open To Work Status on lead accounts and keep only profiles that indicate an Open to work status on LinkedIn, aligning outreach with current intent and cutting prospecting time from hours to minutes. **Marketing Agencies**\ A performance marketing agency is researching creator and talent pipelines where “Open to work” visibility can correlate with availability. They verify LinkedIn Open to Work visibility across many profiles in one run and produce an audit-ready dataset for client reporting. When reviewing “LinkedIn Open to work recruiter only” style cases, the dataset’s `message` field helps flag questionable visibility due to access limitations. **Freelance Researchers**\ A researcher compiling LinkedIn employment intent signals needs consistent, repeatable checks for LinkedIn Open to work profile badge presence. They process a batch of URLs, export results, and use the `message` field to track which checks were clean (`ok`) versus potentially impacted. This makes studies on Open To Work status LinkedIn patterns more manageable. **Automation & Data Engineers**\ A data engineer wants to add a lightweight verification step to an enrichment pipeline. They call the actor, then load `data.open_to_work` and `message` into a warehouse for downstream filtering and monitoring. The stable output structure makes it easier to build dashboards around LinkedIn Open To Work status trends. *** ### How to Run It No code required. Here's how to get your first results in under 5 minutes: 1. **Open the actor on Apify** — go to [console.apify.com](https://console.apify.com) and open the “LinkedIn Open To Work Status” actor page. 2. **Enter your inputs** — add one or more profile URLs in the `startUrls` field. 3. **Configure proxy settings (optional)** — if you use proxy configuration for reliability, set it before starting the run. 4. **Start the run** — launch the actor and monitor the live log for progress. 5. **Open the Dataset tab** — you’ll see results pushed as profiles are processed, including `data.open_to_work` and `message`. 6. **Export your results** — download your dataset in your preferred format from the Apify dashboard. The whole setup takes under 5 minutes — results start appearing within seconds of launch. *** ### Export & Integration Options Once your data is collected, LinkedIn Open To Work Status fits directly into your existing workflow. You can export your dataset from the Apify dashboard as **JSON, CSV, or Excel**. This makes it easy to import into spreadsheets, CRMs, and analyst tools without reformatting. For automation, you can connect the actor using **Apify API access**, and integrate results into tools via **webhooks**, **Zapier**, or **Make**. You can also schedule runs so checks stay current over time—handy when people ask “how to enable Open to Work on LinkedIn” and you want ongoing visibility snapshots. *** ### Pricing LinkedIn Open To Work Status runs on Apify, which includes a **free tier** — no credit card needed to start. You can test with free credits for several real runs, then scale up using Apify’s pay-as-you-go compute model billed per Actor compute unit (CU). For heavier workloads, use Apify’s subscription plans for additional throughput. No per-row markup—your cost is tied to platform compute. Start free at [apify.com](https://apify.com) — scale up when you need to. *** ### Reliability & Limitations | What We Handle | How | |---|---| | Rate-limited access patterns | Retries with resilient request logic | | Blocked or restricted profile views | Returns an explicit auth wall message: `authwall detected (data might be incorrect)` | | Fetch failures | Returns `data.open_to_work: false` plus an error message | | Multi-URL batches | Uses pacing when you provide more than one URL | | Structured dataset output | Consistent `data.open_to_work` and `message` fields pushed to the dataset | **Limitations:** This actor only checks what’s available from the provided profile pages during the run. Private or login-gated visibility may limit what can be detected, and those cases are reflected via the `message` field. For any use case that requires higher assurance, review the `message` values and rerun as needed. For enterprise-scale needs or custom configurations, reach out and we'll help. *** ### Frequently Asked Questions #### Is there a free plan? Yes. Apify offers a free tier with credits so you can test LinkedIn Open To Work status detection before scaling up to larger batches. #### Do I need to log in or create an account on LinkedIn? No. This actor is designed to check publicly accessible profile pages you provide through `startUrls`. #### How accurate is the extracted data? Accuracy depends on what the profile page displays at the time of the run. The actor uses the page content to determine whether LinkedIn Open to Work status indicators are present and returns `data.open_to_work` accordingly. #### How many results can I get per run? You can pass multiple entries in `startUrls`, and the actor will process each provided profile URL. There isn’t a separate “max results” parameter in the input schema—your run size is determined by the number of URLs you submit. #### How fresh is the data? The data is captured during the run. If someone changes their Open To Work status LinkedIn settings after your run starts, the dataset will reflect what was visible at scrape time. #### Is this legal? Does it comply with GDPR / CCPA? Use responsibly. The actor is intended for checking **publicly available data** from profile pages you target, but compliance with GDPR, CCPA, and platform terms is your responsibility. #### Can I export to Google Sheets or Excel? Yes. You can export from the Apify dashboard, then import into Google Sheets or Excel as needed. #### Can I schedule this to run automatically? Yes. You can schedule actor runs using Apify’s scheduling options and keep your LinkedIn Open to Work visibility checks updated automatically. #### Can I access results via the API? Yes. You can run the actor via Apify API and retrieve results programmatically through Apify’s standard interfaces. #### What happens when the actor encounters an error? If a profile fetch fails, it pushes a record with `data.open_to_work: false` and a `message` describing the error. If an auth wall is detected, it pushes a record with `message: "authwall detected (data might be incorrect)"` so you can spot cases where results may not be trustworthy. *** ### Get Help & Use Responsibly Got a question about LinkedIn Open To Work Status or a feature you’d like added? Reach out at . We respond to requests and actively maintain the actor based on user feedback—ideas like batch file input for `startUrls` or richer status messaging are welcome. **Disclaimer:** This actor collects **publicly available data** from profile pages. It does not access private accounts, login-gated pages, or password-protected content. It’s your responsibility to comply with GDPR, CCPA, and platform ToS when using the output. For data-removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `startUrls` (type: `array`): List one or more LinkedIn profile URLs (e.g., https://www.linkedin.com/in/ajjames). ## Actor input object example ```json { "startUrls": [ { "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 = { "startUrls": [ { "url": "https://www.linkedin.com/in/ajjames" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("scrapedrift/linkedin-open-to-work-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 = { "startUrls": [{ "url": "https://www.linkedin.com/in/ajjames" }] } # Run the Actor and wait for it to finish run = client.actor("scrapedrift/linkedin-open-to-work-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 '{ "startUrls": [ { "url": "https://www.linkedin.com/in/ajjames" } ] }' | apify call scrapedrift/linkedin-open-to-work-status --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapedrift/linkedin-open-to-work-status", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Linkedin Open To Work Status", "description": "Extract LinkedIn Open To Work status from profiles at scale. Identify candidates actively seeking opportunities and collect profile details for recruitment, talent sourcing, lead generation, and hiring workflows.", "version": "0.1", "x-build-id": "eISAThcTuyb4ltFw8" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapedrift~linkedin-open-to-work-status/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapedrift-linkedin-open-to-work-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/scrapedrift~linkedin-open-to-work-status/runs": { "post": { "operationId": "runs-sync-scrapedrift-linkedin-open-to-work-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/scrapedrift~linkedin-open-to-work-status/run-sync": { "post": { "operationId": "run-sync-scrapedrift-linkedin-open-to-work-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": [ "startUrls" ], "properties": { "startUrls": { "title": "LinkedIn Profile URLs", "type": "array", "description": "List one or more LinkedIn profile URLs (e.g., https://www.linkedin.com/in/ajjames).", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "URL of a web page", "format": "uri" } } } } } }, "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 } } } } } } } } } } ```