# Laborum Jobs Search Scraper (`jobsapi/laborum-jobs-search-scraper`) Actor

Extract rich, current job listings from Laborum.cl with clean descriptions, job attributes, search context, and stable URLs.

- **URL**: https://apify.com/jobsapi/laborum-jobs-search-scraper.md
- **Developed by:** [Jobs API](https://apify.com/jobsapi) (community)
- **Categories:** Jobs, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 job details

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — 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

## Laborum Jobs Search Scraper

This Apify Actor extracts source-backed public jobs locally or in Apify Cloud from [Laborum.cl](https://www.laborum.cl). It uses the official public `searchV2` and `fichaAvisoNormalizada` HTTPS APIs, enriches each candidate with the normalized detail response, and writes only complete job records to the default dataset.

The implementation does not use an Apify proxy, browser fingerprinting, stealth plugins, or fabricated application URLs. Request metadata, diagnostics, and rejected candidates are kept in KVS records rather than emitted as dataset rows; each response is capped at 5 MB.

### Modes

- `search`: one bounded keyword search, optional client-side location filter.
- `searchMultiple`: bounded searches for several queries with ID deduplication.
- `single`: one official Laborum detail URL.
- `multiple`: several official Laborum detail URLs.
- `startUrls`: a mix of official search and detail URLs.

All modes cap pages, records, concurrency, and request timeouts. Search candidates are enriched through the official normalized-detail endpoint before they can be written.

### Input

```json
{
  "mode": "search",
  "query": "desarrollador",
  "location": "Santiago",
  "maxItems": 3,
  "maxPages": 1,
  "concurrency": 4,
  "requestTimeoutSecs": 25
}
```

Direct modes accept URLs of the form `https://www.laborum.cl/empleos/<slug>-<numeric-id>.html`. Search start URLs may be the home page, `/empleos.html`, or `/empleos-busqueda-<query>.html`.

### Dataset quality

Each row has a stable `laborum-<id>` identifier, canonical public URL, title, employer, structured location, employment/work details, source dates/status, rich plain-text and sanitized HTML descriptions, headings/sections/bullets, requirements, qualifications, benefits, salary fields when published, explicit application links when published, raw source provenance, request receipts, and verification flags. Null, blank, and empty values are removed before writing. Records must pass identity, canonical URL, HTTP 200, and description-completeness checks.

The dataset schema is strict (`.actor/dataset_schema.json`). Run state is stored under `RUN_SUMMARY`, `RUN_DIAGNOSTICS`, `RUN_SKIPS`, `REQUEST_RECEIPTS`, `RUN_HEALTH`, and `RUN_METADATA`.

### Local development

```text
npm install
npm test
npm run lint
npm run check
npm run validate
npx --yes apify-cli run --purge --input-file INPUT.json
```

The repository's reproducible inputs include `INPUT-single.json`, `INPUT-multiple.json`, `INPUT-search-multiple.json`, `INPUT-start-urls.json`, and `INPUT-negative.json`. The negative input verifies that a missing official detail produces a structured KVS diagnostic and no dataset row.

### Responsible use

Use the Actor only for publicly available information, respect Laborum's terms and applicable law, and keep request limits bounded. A target-side access block is reported honestly; it is not bypassed.

# Actor input Schema

## `mode` (type: `string`):

search discovers jobs; searchMultiple runs several queries; single and multiple enrich exact detail URLs; startUrls accepts official search or detail URLs.

## `query` (type: `string`):

Spanish job title, skill, or keyword.

## `queries` (type: `array`):

Queries for searchMultiple mode.

## `location` (type: `string`):

Optional Chilean city or region used to retain matching listings.

## `url` (type: `string`):

One official Laborum /empleos/<slug>-<numeric-id>.html URL for single mode.

## `urls` (type: `array`):

Official Laborum detail URLs for multiple mode.

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

Official Laborum search or detail URLs for startUrls mode.

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

Maximum complete records to write.

## `maxPages` (type: `integer`):

Bounded number of official search API pages per query.

## `concurrency` (type: `integer`):

Maximum concurrent official detail API requests.

## `requestTimeoutSecs` (type: `integer`):

Timeout per official API request in seconds.

## Actor input object example

```json
{
  "mode": "search",
  "query": "desarrollador",
  "location": "Santiago",
  "maxItems": 3,
  "maxPages": 3,
  "concurrency": 4,
  "requestTimeoutSecs": 25
}
```

# Actor output Schema

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

Complete source-backed public Laborum job records.

## `runState` (type: `string`):

Summary, diagnostics, skips, request receipts, health, and runtime metadata.

# 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 = {
    "mode": "search",
    "query": "desarrollador",
    "location": "Santiago",
    "maxItems": 3,
    "maxPages": 3,
    "concurrency": 4,
    "requestTimeoutSecs": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/laborum-jobs-search-scraper").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 = {
    "mode": "search",
    "query": "desarrollador",
    "location": "Santiago",
    "maxItems": 3,
    "maxPages": 3,
    "concurrency": 4,
    "requestTimeoutSecs": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/laborum-jobs-search-scraper").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 '{
  "mode": "search",
  "query": "desarrollador",
  "location": "Santiago",
  "maxItems": 3,
  "maxPages": 3,
  "concurrency": 4,
  "requestTimeoutSecs": 25
}' |
apify call jobsapi/laborum-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/laborum-jobs-search-scraper"
        }
    }
}

```

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/dsSbEJHe3NdIlRVAe/builds/PEsq4YdS0fUmfd33W/openapi.json