# InfoJobs Scraper (`bovi/infojobs-scraper`) Actor

Extract job listings from InfoJobs.net, Spain's leading job board. Get title, company, salary range, location, contract type and requirements for any search query. Structured JSON output, pay per result.

- **URL**: https://apify.com/bovi/infojobs-scraper.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $37.83 / 1,000 job listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## InfoJobs Spain Job Listings Scraper

InfoJobs Job Scraper 🇪🇸 is an evidenced Store rival with a Spain-focused promise to extract job titles, descriptions, and company details for market analysis and recruitment research. This actor addresses the same buyer intent with a more explicit workflow around configurable `queries` or `startUrls`, bounded runs, proxy settings, and inspection of reusable Apify dataset records; it does not claim broader country coverage or richer fields than the source returns.

Brazil Jobs Scraper — InfoJobs, Vagas, Gupy, LinkedIn is another evidenced rival, positioned around combining five Brazilian job boards and fields such as salary, benefits, experience level, and work model. That breadth is useful for cross-board Brazilian research, while this actor is intentionally narrower and better suited to buyers who need focused InfoJobs collection, repeatable search inputs, and a clearly documented validation step instead of an unsupported promise of multi-board coverage.

### What this actor does

The actor collects job-search results from InfoJobs and writes structured records to the Apify dataset. It is suitable for:

- Recruitment research and talent-market discovery.
- Comparing recurring searches by role, company, or location.
- Employment and job-market monitoring.
- Building a bounded input dataset for spreadsheets, warehouses, or internal automation.
- Exporting collected records as JSON or CSV after review.

The available inputs are:

- `queries` — search terms or query definitions accepted by the current actor schema.
- `startUrls` — InfoJobs search URLs to collect.
- `maxItems` — an upper bound for a run.
- `proxyConfiguration` — proxy settings appropriate for the access environment.

Always open the current input schema before running. Input names, accepted shapes, and returned fields are implementation details and may change.

### Recommended workflow

1. Start with one narrowly scoped query or search URL.
2. Set a small `maxItems` value for validation.
3. Configure a suitable proxy only when required by the source or your operating environment.
4. Run the actor and inspect several dataset records.
5. Confirm which title, description, company, location, salary, and URL fields are present for your search.
6. Adjust the query or limit, then export the verified dataset or connect it to downstream processing.
7. For monitoring, retain the query, URL, run date, and filtering choices so later runs remain comparable.

### Output and dataset use

The run writes records to the default Apify dataset. The exact schema depends on the source response and actor implementation, so treat sample records from your own run as the source of truth. Records can be reviewed in Apify and exported to JSON or CSV. Do not build a production integration around an assumed field until it has been observed in representative results.

### Limitations and responsible use

The actor does not guarantee complete coverage of InfoJobs, a fixed number of results, real-time freshness, stable fields, or uninterrupted execution. Results can vary with query wording, search availability, pagination, response changes, access conditions, proxy behavior, and source-side restrictions. A failed or partial run should be reviewed rather than interpreted as proof that no matching jobs exist.

Use only data and access methods you are permitted to use. Respect InfoJobs terms, applicable laws, privacy requirements, rate limits, and any restrictions on storing or redistributing job or personal information. This actor is a collection tool, not a guarantee that a listing is current, genuine, available, or suitable for a hiring decision.

### Quick-start example

Review the current schema, provide a focused query or InfoJobs search URL, set `maxItems` to a conservative test value, and run the actor. Inspect the resulting dataset before scaling the run or automating an export.

# Actor input Schema

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

Array of search strings

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

Direct infojobs.net search-result URLs, e.g. with your own province/contract/teleworking filters applied on the site (jobsearch/search-results/list.xhtml?...)

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

Maximum number of items to scrape

## `proxyConfiguration` (type: `object`):

Proxy settings

## Actor input object example

```json
{
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset with the scraped records.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/infojobs-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("bovi/infojobs-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 '{}' |
apify call bovi/infojobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/infojobs-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/hu6YSLFD0keQLcbNB/builds/j1j6cNv27KxCqoJwB/openapi.json