# Expired Jobs API for Advanced LinkedIn Job Search API (`jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api`) Actor

Find native LinkedIn job pages explicitly marked No longer accepting applications, via a public content API requesting a fresh recrawl. No API key. Current closed-status snapshots; no inferred expiry date or filled-vacancy claim. Provider does not expose per-URL crawl timestamps.

- **URL**: https://apify.com/jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api.md
- **Developed by:** [Jobs Scraper](https://apify.com/jobscrawler) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What this Actor does

Observe explicit closed-to-applications status on actual native LinkedIn job-view pages. The Actor requires the native job ID and title plus the exact header label “No longer accepting applications”. A phrase found only in a job description, an active page, unrelated profile or missing document is not a closed-status result.

The keyless default uses Exa's public MCP content-search API. Every request uses search type auto and maxAgeHours=0. This is the provider's documented always-live-crawl contract. Cached fallback and cache-only search types are never used. No vendor API key, source login, generated cookie, browser identity change or scraping proxy is required.

Freshness is supplied by this provider contract. The public tool does not expose individual crawl timestamps or native HTTP statuses; the Actor explicitly records directSourceNetworkVerified=false and sourceCrawlTimestampKnown=false. It does not pretend that a direct native fetch or an exact crawl timestamp was independently verified.

### Scope and defaults

This is a current closed-status snapshot, replacing the previous credential-only rolling expired-ID feed as the default. It does not establish when a job expired, whether it was closed by the poster, or whether an employer filled the vacancy. Older postings can be observed closed today. exactExpirationTimeKnown and sourceVacancyFilledStatusKnown remain false. timeRange must be all; recent-expiration windows are rejected rather than invented.

Example input:

```json
{
  "searchQuery": "Data Analyst",
  "maxItems": 10,
  "timeRange": "all",
  "sampleMode": false
}
```

A nonempty startUrls list restricts output to specific native LinkedIn job IDs. The default searches for Data Analyst postings with an explicit native closed header. maxItems is a cap, not a promise to fabricate missing records. The Actor deduplicates by native job ID and fails when no qualifying actual source document is available.

### Output and provenance

Results contain native jobId, jobTitle, jobUrl, the combined source employer/location header, observedClosedAt and qualified closed status. observedClosedAt is when the provider response was retrieved, not an invented expiry date. No exact expiration timestamp is emitted. Every record includes its actual provider request ID, source-text SHA-256, native header evidence and the forced-fresh policy. Missing optional fields are omitted, not replaced with nulls, placeholders or synthetic values.

Two anonymized examples illustrate the output shape only:

```json
[
  {
    "jobId": "1234567890",
    "jobTitle": "Example Analyst",
    "jobUrl": "https://www.linkedin.com/jobs/view/1234567890",
    "expirationStatus": "closed_to_applications",
    "exactExpirationTimeKnown": false,
    "dataMode": "live_public_search_recrawl"
  },
  {
    "jobId": "2345678901",
    "jobTitle": "Example Engineer",
    "jobUrl": "https://www.linkedin.com/jobs/view/2345678901",
    "expirationStatus": "closed_to_applications",
    "exactExpirationTimeKnown": false,
    "dataMode": "live_public_search_recrawl"
  }
]
```

### Limits and failure handling

The public provider can impose rate or availability limits. Failed requests, provider errors, missing text, source mismatches and no-result responses fail the run; no stale fallback is substituted. Requests and response sizes are bounded, and source HTML or text is never executed as code.

Inspect SOURCE_METADATA for the actual request, forced freshness policy and returned source documents. RUN_SUMMARY reports actual counts. ERROR_DIAGNOSTIC is separate from the dataset. Local CLI evidence and Apify production datasets are distinct. Maintenance should be cleared only after genuine nonempty output has passed current local and production verification.

Provider references: [Exa Contents freshness controls](https://exa.ai/docs/reference/get-contents) and [the official public MCP implementation](https://github.com/exa-labs/exa-mcp-server/blob/main/src/tools/webSearchAdvanced.ts). Apify execution and configured result-event charges apply in the cloud. Public-provider availability is not guaranteed.

# Changelog

This Actor's version history is a separate document: https://apify.com/jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api/changelog.md

# Actor input Schema

## `searchQuery` (type: `string`):

Keywords for native LinkedIn job-view pages with explicit closed-to-applications headers.

## `startUrls` (type: `array`):

Up to ten native LinkedIn job-view URLs. A nonempty list restricts output to these exact native IDs.

## `timeRange` (type: `string`):

Current observed closed status only. Exact closure times and rolling expired-date windows are not supplied.

## `maxItems` (type: `integer`):

Result cap. Invalid, duplicate, incomplete or unrelated source documents are excluded; no padding.

## `sampleMode` (type: `boolean`):

Must be false. Only current public provider results are used.

## Actor input object example

```json
{
  "searchQuery": "Data Analyst",
  "startUrls": [],
  "timeRange": "all",
  "maxItems": 10,
  "sampleMode": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

Actual source records.

## `files` (type: `string`):

Source metadata, provider documents and separate failures.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQuery": "Data Analyst",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQuery": "Data Analyst",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQuery": "Data Analyst",
  "maxItems": 10
}' |
apify call jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobscrawler/expired-jobs-api-for-advanced-linkedin-job-search-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/bIenBeQtfruZ7DcXY/builds/TsgNcJHVe2hTTNsTo/openapi.json