Apify logo

Get LinkedIn Job Listings (Apify)

Apify → Get LinkedIn Job Listings (Apify)

POST/v1/apify-find-active-job-openings
texau__apify-find-active-job-openingsenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/apify-find-active-job-openings
{
  "title": "sample-value",
  "location": "sample-value",
  "row": 1,
  "company_name": "Acme, Inc.",
  "published_at": "sample-value",
  "work_type": "sample-value",
  "contract_type": "sample-value",
  "experience_level": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "job_id": "rec_4f3a91",
    "title": "sample",
    "company_name": "sample",
    "location": "sample",
    "published_at": "sample",
    "posted_time": "sample",
    "salary": "sample",
    "job_url": "https://acme.com",
    "apply_url": "https://acme.com",
    "application_count": 1,
    "experience_level": "sample",
    "contract_type": "sample",
    "work_type": "sample",
    "sector": "sample"
  }
}

Retrieves active LinkedIn job listings matching specified search criteria using Apify.

Install

Add get linkedin job listings (apify) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__apify-find-active-job-openings

When to use this.

The apify-find-active-job-openings action enables users to retrieve active job listings from LinkedIn that match specified search criteria, enhancing the job search process. Key input parameters include 'title' for job title keywords, 'location' for geographical targeting, and 'companyName' to filter by specific employers. Additional filters such as 'publishedAt', 'workType', 'contractType', and 'experienceLevel' allow for more tailored results. The output includes essential job details such as job ID, title, company name, location, salary, and application URLs, all formatted as semantic types like text and URL. This action is particularly useful for job seekers, recruiters, and HR professionals looking to streamline their hiring processes or find suitable employment opportunities, making it a valuable tool in the enrichment category.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Get LinkedIn Job Listings (Apify)

Try it

The job title keyword to search for (e.g. Engineer, Web Developer).

The job location (e.g. United States, India, New York).

Number of rows to display.

Company names to filter by (e.g. Google, Airbnb).

Filter jobs by publish time.

Work type filter.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • job_id
    Job Id
    nullablestring
  • title
    Title
    string
  • company_name
    Company Name
    string
  • location
    Location
    nullablestring
  • published_at
    Published At
    nullablestring
  • posted_time
    Posted Time
    string
  • salary
    Salary
    nullablestring
  • job_url
    Job Url
    string
  • apply_url
    Apply Url
    nullablestring
  • application_count
    Application Count
    string
  • experience_level
    Experience Level
    nullablestring
  • contract_type
    Contract Type
    nullablestring
  • work_type
    Work Type
    nullablestring
  • sector
    Sector
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/apify-find-active-job-openings. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/apify-find-active-job-openings
curl -X POST 'https://v3-api.texau.com/api/v1/apify-find-active-job-openings' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"title":"sample-value","location":"sample-value","row":1,"company_name":"Acme, Inc.","published_at":"sample-value","work_type":"sample-value","contract_type":"sample-value","experience_level":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "job_id": "rec_4f3a91",
    "title": "sample",
    "company_name": "sample",
    "location": "sample",
    "published_at": "sample",
    "posted_time": "sample",
    "salary": "sample",
    "job_url": "https://acme.com",
    "apply_url": "https://acme.com",
    "application_count": 1,
    "experience_level": "sample",
    "contract_type": "sample",
    "work_type": "sample",
    "sector": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get LinkedIn Job Listings (Apify)→Search LinkedIn Sales Navigator People (Apify)→Search LinkedIn Profiles (Apify)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → get linkedin job listings (apify) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get LinkedIn Job Listings (Apify)Apify action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit30 / min
  • Per-day limit1,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Standard tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Apify actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__apify-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Get LinkedIn Job Listings (Apify) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs