# Linkedin Open To Work Status (`scraperoka/linkedin-open-to-work-status`) Actor 🔎 Open to Work! I’m exploring new opportunities in tech & data. Passionate about building scalable solutions, turning insights into impact, and collaborating cross-functionally. 🚀 Let’s connect! - **URL**: https://apify.com/scraperoka/linkedin-open-to-work-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 To Work Status 🎯 — Detect “Open to Work” on LinkedIn profiles in minutes Manually checking hundreds of LinkedIn profiles for **Open to Work status** wastes hours you don’t have. **LinkedIn Open To Work Status** automatically checks profiles and returns whether the person is marked as open to work—so you can build cleaner outreach lists faster. This **LinkedIn Open To Work status** detector (and related **LinkedIn Open To Work status meaning** checks) is ideal for marketers, recruiters, and growth teams who need quick, structured answers at scale. In a single run, you can process multiple profile URLs and get results you can export right away—no guesswork. --- ### What You Get: Sample Output Here’s a sample record from a single run: ```json { "data": { "open_to_work": true }, "message": "ok" } ```` If the actor can’t fetch a profile, you’ll instead see an error result like: ```json { "data": { "open_to_work": false }, "message": "error: " } ``` | Field | Type | What It Tells You | |---|---|---| | `data.open_to_work` | boolean | The core decision: whether the profile appears to be marked “Open to work” | | `message` | string | The run status for that profile (for example, `ok`, `authwall detected (data might be incorrect)`, or an `error: ...` message) | | `data` | object | Grouped result payload you can safely parse in pipelines | | `data.open_to_work` (failure case) | boolean | When errors happen, the actor defaults to `false` so your workflows don’t break | | *(Dataset metadata)* `completed.linkedin_url` | string | The scraped profile URL saved in the dataset (useful for auditing) | | *(Dataset metadata)* `data.open_to_work` | boolean | Same boolean stored in the dataset view (“Open to Work?”) | | *(Dataset metadata)* `message` | string | Same status text stored in the dataset view | | *(Dataset metadata)* `completed.created` | string | Scrape time, so you can track freshness of **LinkedIn open to work visibility options** checks | Export your dataset as JSON, CSV, or Excel — straight from the Apify dashboard. *** ### Why LinkedIn Open To Work Status? There are a lot of ways to pull profile signals from LinkedIn — here’s what sets **LinkedIn Open To Work Status** apart. #### Clear “Open to Work” signal detection This actor focuses on whether a profile is marked as open to work and returns a simple boolean (`data.open_to_work`). It also handles common status wording patterns like “seeking opportunities,” helping with cases like **LinkedIn open to work wrong status**. #### Output that’s easy to use in outreach workflows Results are written in a consistent JSON shape (`data.open_to_work` plus a `message`) so you can filter immediately in your CRM or spreadsheet. This is helpful when you’re deciding **open to work on LinkedIn** settings for targeting and segmentation. #### Built-in resilience for real-world scraping It includes retries for failed fetch attempts and provides explicit messaging when an authentication wall is detected (so you can avoid silent bad reads). That makes it more reliable for bulk runs across many profiles. #### Structured dataset storage for auditability In the dataset view, you’ll see the profile URL, the boolean “Open to Work?” value, the status message, and the scrape time. This makes it easier to validate **LinkedIn open to work recruiters only** vs public visibility scenarios in your results. *** ### Configuring Your Run Drop this into your `input.json` to get started: ```json { "startUrls": [ { "url": "https://www.linkedin.com/in/ajjames" } ] } ``` | Parameter | Required | What It Does | |---|---:|---| | `startUrls` | ✅ | List of one or more LinkedIn profile URLs to check (each entry should be an object with `url`). | *** ### Core Capabilities #### Fast bulk checks from profile URLs Feed in multiple profile links via `startUrls`, and the actor processes them one by one (with an additional pacing delay for larger lists). It’s built for collecting **LinkedIn Open To Work status** signals across a target list. #### Simple, actionable boolean output You get `data.open_to_work` as a boolean, making it straightforward to filter for outreach eligibility—useful for **LinkedIn open to work public** vs other visibility expectations and diagnosing **LinkedIn Open To Work status meaning**. #### Clear per-profile status messaging Each processed profile includes a `message` field so you can distinguish normal results (`ok`) from cases where the actor detected an authwall or hit an error. This helps you handle **LinkedIn open to work not showing** situations in your workflow. #### Retries and fallback handling for resilience If fetching a profile fails, the actor retries before recording an error result. When an error occurs, it outputs `data.open_to_work: false` along with an error message so downstream steps remain stable. #### Dataset-friendly structure and export Each result is pushed into the Apify dataset with the dataset view configured to show: `completed.linkedin_url`, `data.open_to_work`, `message`, and `completed.created`. You can export instantly for analysis or segmentation. *** ### Who Gets the Most Out of This **Recruiters and talent sourcers** can use LinkedIn Open To Work status to prioritize candidates who may be actively seeking roles, turning a long **Open to work on LinkedIn** verification task into a structured boolean list. **Sales and SDR teams** benefit when building targeted outbound segments; they can quickly separate profiles likely to be receptive based on `data.open_to_work`, then enrich campaigns without manual checking. **Growth teams and ops leads** can automate lead list cleanup by consistently flagging Open to Work signals and tracking scrape time (`completed.created`) to understand how **LinkedIn open to work status** changes over time. **Data analysts and researchers** can run experiments on “status vs outcomes” by exporting the dataset and joining it with their own CRM or campaign data, while keeping an audit trail through the saved profile URLs. **Developers and automation specialists** can integrate the results into their pipeline since the actor outputs consistent JSON with `data.open_to_work` and a `message`, supporting reliable downstream filtering. *** ### Step-by-Step: How to Use It No coding needed. Here's how to run LinkedIn Open To Work Status from start to finish: 1. **Open the actor on Apify** — visit [console.apify.com](https://console.apify.com) and open the actor page. 2. **Enter your inputs** — add your profile links in `startUrls` as an array of `{ "url": "..." }` entries. 3. **Configure proxy settings (optional)** — if you use proxy configuration in your runs, enable it for better reliability on bulk lists. 4. **Hit Run and watch the live log** — review progress and per-profile messages (including error or authwall notices). 5. **View results in the dataset tab** — confirm `data.open_to_work` and the `message` for each profile. 6. **Export your data** — download results as JSON, CSV, or Excel from the dataset view. 7. **Iterate** — rerun with updated URLs to keep your **LinkedIn Open To Work status** dataset fresh. The whole process takes under 5 minutes to set up. *** ### Integrations & Export Options Once your data is collected, LinkedIn Open To Work Status plugs directly into your existing workflow. You can export your dataset formats (including JSON, CSV, and Excel) directly from the Apify dataset tab. That makes it easy to move **LinkedIn Open To Work status** results into spreadsheets for **LinkedIn open to work location settings**-style segmentation workflows. For automation, you can connect the actor to your stack via Apify’s API, scheduled runs, and webhook-style triggers. If you use no-code tools like Zapier or Make, you can push results to your CRM or downstream pipeline without manual copy-paste—perfect for recurring lead enrichment. For deeper details, see Apify documentation: https://apify.com/docs/api *** ### Pricing & Free Trial LinkedIn Open To Work Status runs on the Apify platform, which offers a **free tier** — no credit card required to get started. On Apify, you can typically run small tests with limited credits, then scale as needed. For production usage, costs are generally based on Apify platform compute units (CU) rather than a per-row charge. Start for free at [apify.com](https://apify.com) and scale when you're ready. *** ### Reliability & Performance | What We Handle | How | |---|---| | Rate limiting and unstable fetches | Retries are included for failed requests to reduce one-off failures | | Access/authwall issues | Detects an authwall scenario and returns an explicit message so you can avoid trusting uncertain reads | | Multi-URL runs | Adds pacing when processing multiple profiles to improve stability | | Error transparency | On errors, it pushes a result with `data.open_to_work: false` and an `error: ...` message | **Limitations:** This actor works with publicly accessible profile pages and relies on what’s visible in the HTML content at the time of the scrape. If a profile requires login to view or doesn’t show relevant status text, results may be incomplete. For enterprise-scale runs, contact us to discuss custom configurations. *** ### Frequently Asked Questions #### Is there a free plan or trial? Yes. Apify offers a **free tier** for getting started with actors, which is typically enough for several test runs before you scale up. #### Do I need to log in to LinkedIn to use this? No. You only provide profile URLs in `startUrls`, and the actor checks the publicly viewable content it can access for **LinkedIn Open To Work status**. #### How accurate is the data? Accuracy depends on what is visible on the target profile page. The actor uses visible page signals to decide `data.open_to_work` and reports a `message` when an authwall is detected, helping you trust the output appropriately. #### How many results can I get per run? You can submit one or more URLs in `startUrls`, and the actor processes each profile and writes results to the dataset. The exact practical limits depend on your Apify run configuration and platform conditions. #### How often is the data updated / how fresh is it? Data freshness depends on when you run the actor. The dataset includes `completed.created` (scrape time), so you can tell when the **LinkedIn open to work status** check was performed. #### Is this legal? Does it comply with GDPR / CCPA? Yes for using **publicly available data**, but compliance depends on your use case. You should ensure your collection, storage, and processing follow GDPR, CCPA, and applicable platform rules for the data you use. #### Can I export results to Google Sheets or Excel? Yes. You can export the Apify dataset to formats like JSON, CSV, or Excel from the Apify dashboard, then import into tools such as Google Sheets or your spreadsheet of choice. #### Can I run this on a schedule automatically? Yes. You can schedule actor runs on Apify so **LinkedIn Open To Work status** checks happen regularly without manual triggering. #### Can I access this via API? Yes. You can call and retrieve results programmatically using Apify API features. #### What happens if the actor hits an error? If the actor fails to fetch a profile, it pushes a result with `data.open_to_work: false` and a `message` that includes an `error: ...` description. If an authwall is detected, it sets `message` to `authwall detected (data might be incorrect)`. *** ### Need Help or Have a Request? Got a question about **LinkedIn Open To Work status** or want a new feature added? Reach out at . We actively maintain this actor and can also discuss enhancements like webhook notifications on completion or additional output fields for easier segmentation. *** ### Disclaimer & Responsible Use *LinkedIn Open To Work Status is the fastest, most reliable way to detect Open to Work signals from public profiles — start your free run today.* This actor collects **publicly available data** and does not access private accounts, login-gated content, or password-protected pages. It’s your responsibility to comply with GDPR, CCPA, applicable platform ToS, and any local regulations for how you store and use the data. 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("scraperoka/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("scraperoka/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 scraperoka/linkedin-open-to-work-status --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/linkedin-open-to-work-status", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Linkedin Open To Work Status", "description": "🔎 Open to Work! I’m exploring new opportunities in tech & data. Passionate about building scalable solutions, turning insights into impact, and collaborating cross-functionally. 🚀 Let’s connect!", "version": "0.1", "x-build-id": "Hi0DkR399P3CzNK4X" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~linkedin-open-to-work-status/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-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/scraperoka~linkedin-open-to-work-status/runs": { "post": { "operationId": "runs-sync-scraperoka-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/scraperoka~linkedin-open-to-work-status/run-sync": { "post": { "operationId": "run-sync-scraperoka-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 } } } } } } } } } } ```