Empléate.gob.es Jobs Scraper (Spain) avatar

Empléate.gob.es Jobs Scraper (Spain)

Pricing

from $1.60 / 1,000 job postings

Go to Apify Store
Empléate.gob.es Jobs Scraper (Spain)

Empléate.gob.es Jobs Scraper (Spain)

SEPE Empléate jobs: job postings from Empléate, Spain's official public employment service (SEPE) job board, with title, company, salary when published, province, contract type and full description. Spain job data as JSON, no login.

Pricing

from $1.60 / 1,000 job postings

Rating

0.0

(0)

Developer

Vivien MORVAN

Vivien MORVAN

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

Empléate Jobs Scraper: Keyword & URL Search (Spain)

Scrape job postings from Empléate, Spain's official public employment service (SEPE/SNE) job board, by keyword, province, category, or by pasting a search URL copied straight from the site: title, category, province, city, coordinates, contract type, work schedule and full description.

At a glance

What you getPublic employment service (SEPE) postings from Empléate: title, category, province, city, contract type, work schedule, education required, date, description.
Price$2.00 per 1,000 postings: a 50-posting test run costs about $0.11, start fee included.
Speed50 postings in about 15 seconds. No login, no proxy, no browser to configure.
Try itClick Try for free: the form is already filled with province MADRID.
Keyword & URL searchType keywords/province/category, or paste one or more search result URLs copied from empleate.gob.es: see "Paste a search URL" below.
Keep it freshSchedule it daily and keep only the new postings: see "Monitor new postings daily" below.

What you can do with it

  • Monitor the Spanish public job market: new postings by category or province, updated daily.
  • Feed a job alert or an aggregator: run it on a schedule and dedupe by id to catch only the new postings.
  • Map job demand by region: every posting carries province, city and coordinates.
  • Track disability-friendly postings: a boolean flag marks offers reserved for workers with a disability certificate.
  • Paste a search URL: already filtered by keyword and province on empleate.gob.es? Copy the page's address (for example https://www.empleate.gob.es/empleo/#/trabajo?search=enfermera&pag=0&provincia=28) into Search URLs and the actor applies the same filters, no need to re-type them. Combine several URLs, or mix them with the Keywords/Province fields: every search's results are merged and de-duplicated, up to the maximum number of postings.

Input

FieldWhat it does
KeywordsJob title or skill, in Spanish, for example programador or enfermera. Leave empty to get every active posting.
ProvinceSpanish province name as Empléate labels it, for example MADRID or BARCELONA. Leave empty for all of Spain.
CategoryEmpléate job category, for example INFORMÁTICA/TELECOMUNICACIONES or SALUD/DEPORTE. Leave empty for all categories.
Search URLs (optional)Paste one or more search result URLs copied from empleate.gob.es, for example https://www.empleate.gob.es/empleo/#/trabajo?search=programador&pag=0. Each URL runs as its own search, applying its own keyword and province filters, in addition to Keywords/Province/Category above.
Published within (days)Keep only postings published in the last N days. Use 1 for a daily monitoring run.
Maximum number of postingsThe run stops once this many postings are saved.
Include full descriptionsAdd the full job description as plain text.

Output

One record per posting, with two layers of fields:

  • Unified fields (same names on every job-posting actor by this author, schema.org JobPosting vocabulary): id, url, title, companyName, companyUrl, confidentialCompany, locationLabel, city, region, postalCode, remote, employmentType, salaryMin, salaryMax, salaryCurrency, salaryPeriod, datePosted, validThrough, description, experienceLevel, industry, skills, source, sourceId, scrapedAt. Empléate never discloses an employer name (companyName is always null, confidentialCompany always true) and has no structured salary field (always null); remote is always unknown for the same reason: the site carries no teleworking field at all. There is one deliberate exception: the site's own country field below already carries the human label "ESPAÑA" under that exact name, so the ISO-code country field of the unified schema is not duplicated under the same key — all postings are from Spain (ES) regardless.
  • Site-specific fields, kept exactly as before for compatibility with existing integrations: category, subcategory, region, province, city, country, latitude, longitude, contractType, workSchedule, positionsOffered, educationRequired, disabilityFriendly, sourceSystem, applyUrl, sourceUrl, publishedAt, expiresAt.

Three real postings from an actual run (province MADRID, 25/10/2026; descriptions shortened):

[
{
"id": "1858669551",
"url": "https://www.empleate.gob.es/empleo/",
"title": "CAMAREROS/AS",
"companyName": null,
"locationLabel": "Madrid, MADRID",
"remote": "unknown",
"employmentType": "part_time",
"datePosted": "2026-10-25T18:24:39Z",
"industry": "HOSTELERÍA/TURISMO",
"source": "empleate.gob.es",
"category": "HOSTELERÍA/TURISMO", "province": "MADRID", "city": "Madrid", "country": "ESPAÑA",
"contractType": "Temporary", "workSchedule": "PARCIAL", "disabilityFriendly": false,
"description": "Se necesitan CAMAREROS/AS para trabajar en evento THE GOLDEN IBÉRICA BURGER…"
},
{
"id": "1858668839",
"url": "https://www.tecnoempleo.com/desarrollador-java-microservicios-serem/spring-boot-maven/rf-d7541a16e2e093075e46?lang=es&utm_source=empleate",
"title": "Desarrollador/a Java / Microservicios, hibrido",
"companyName": null,
"locationLabel": "Madrid, MADRID",
"remote": "unknown",
"employmentType": "full_time",
"datePosted": "2026-10-25T15:33:30Z",
"industry": "INFORMÁTICA/TELECOMUNICACIONES",
"source": "empleate.gob.es",
"category": "INFORMÁTICA/TELECOMUNICACIONES", "province": "MADRID", "city": "Madrid", "country": "ESPAÑA",
"contractType": "Indefinido", "workSchedule": "COMPLETA", "disabilityFriendly": false,
"description": "Desarrollador/a Java / Microservicios Desde Serem buscamos un/a Desarrollador/a Java Senior…"
},
{
"id": "1858624168",
"url": "https://www.empleate.gob.es/empleo/",
"title": "MOZO DE ALMACÉN. ZONA HUMANES.",
"companyName": null,
"locationLabel": "Fuenlabrada, MADRID",
"remote": "unknown",
"employmentType": "unknown",
"datePosted": "2026-10-24T00:48:07Z",
"industry": "CONDUCTORES/TRANSPORTE",
"source": "empleate.gob.es",
"category": "CONDUCTORES/TRANSPORTE", "province": "MADRID", "city": "Fuenlabrada", "country": "ESPAÑA",
"contractType": "Contract", "workSchedule": "COMPLETA", "disabilityFriendly": false,
"description": "FUNCIONES: Recepción material, preparación pedidos, introducción de albaranes en sistema…"
}
]

Export the dataset as JSON, CSV or Excel, or read it through the Apify API.

Why this one

  • Official public source, no scraping of a private aggregator. Postings come straight from SEPE and its regional partners (SOC, LABORA, and others).
  • Coordinates included. Every posting carries latitude and longitude for mapping, not just a province name.
  • No login, no CV upload. Everything comes from the board's own public search.

Good to know

  • Empléate does not publish an employer name or a structured salary field for most postings: this is how the board itself works, not a gap in the actor. A salary figure sometimes appears inside the free-text description instead.
  • A line that carries an office or application-portal e-mail address is dropped from the description: no contact data is collected.
  • Most postings have no outbound application link (applyUrl is empty): applicants apply through Empléate itself or through the regional portal named in the description.
  • No browser needed: runs are fast and cheap.
  • A Search URLs entry that isn't an empleate.gob.es search page (another site, the bare homepage, a job detail page, a login or profile page) is skipped with a warning in the log, not a failed run, as long as another URL or the Keywords/Province/Category fields still produce something. A filter inside the URL that the actor doesn't recognize is named in the same way and ignored; the ones it does apply are search (keywords) and provincia (province).

En español

Este actor extrae las ofertas del portal público Empléate (SEPE): puesto, categoría, provincia, ciudad, tipo de contrato, jornada, formación requerida, fecha y descripción, en JSON, CSV o Excel. Sirve para alertas de empleo público por provincia o agregadores. No necesita cuenta ni proxy; datos públicos del Estado.

Why this one

  • Official public source, no scraping of a private aggregator. Postings come straight from SEPE and its regional partners (SOC, LABORA, and others).
  • Coordinates included. Every posting carries latitude and longitude for mapping, not just a province name.
  • No login, no CV upload. Everything comes from the board's own public search.

Who uses it

  • Recruiting agencies and HR teams watch which companies hire, for which roles and at which salary, in their market.
  • Job boards and aggregators feed their own site with fresh postings in a stable schema, without maintaining a parser.
  • B2B sales and lead generation: a company that is hiring is a company that is buying. Filter postings by role to spot prospects early.
  • Labour-market research: salaries, skills in demand, remote share and hiring volume over time.

Pricing

Pay per result: $2.00 per 1,000 postings, plus $0.01 per run start with the default 4 GB of memory. For example, 100 postings cost about $0.21. You only pay for the postings you receive, and platform usage is included in that price. Store discounts apply automatically on paid Apify plans: up to 20% off every event on the higher tiers.

Run it from your code

JavaScript:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('bibian/empleate-jobs-scraper').call({
province: 'MADRID',
searchUrls: ['https://www.empleate.gob.es/empleo/#/trabajo?search=programador&pag=0'],
maxItems: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python:

from apify_client import ApifyClient
client = ApifyClient(token="<APIFY_TOKEN>")
run = client.actor("bibian/empleate-jobs-scraper").call(run_input={
"province": "MADRID",
"searchUrls": [
"https://www.empleate.gob.es/empleo/#/trabajo?search=programador&pag=0"
],
"maxItems": 50
})
items = client.dataset(run["defaultDatasetId"]).list_items().items

Monitor new postings daily and connect your tools

  1. Schedule it. Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Deduplicate on the id field if you keep your own copy. Tick Only new results in the input and each run returns, and charges, only the postings that earlier runs of the same search did not deliver.
  2. Push the results where you work. Add an Apify integration or a webhook to the task: Google Sheets, Slack, Make, Zapier, n8n or your own endpoint, triggered at the end of every run.
  3. Call it from your stack. The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
  4. Let an AI agent use it. Through the Apify MCP server, assistants such as Claude or ChatGPT can search the Store, read this page and run the actor as a tool.

Frequently asked questions

Do I need an account, cookies or a proxy for Empléate? No. The actor reads publicly visible pages only.

Which formats can I export? JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.

Is it legal to scrape? The actor collects publicly visible postings and respects the robots.txt rules of the site. How you use the data is your responsibility: check the site's terms and the laws that apply to you, for example the GDPR.

Need another site, a missing field or a new filter? Open an issue in the Issues tab and say what you need, with an example URL if you have one. Requests are read, and the most asked ones are built next.

Need a custom version built for you? I also build private versions and custom scrapers: another site, extra fields, a specific output format, or delivery straight to Google Sheets, a database or a webhook. Open an issue in the Issues tab with what you need and an example URL, and I will reply there with a quote.

Something does not work? Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.

Did this save you time? A short review on the Store page helps other people find the actor, and tells me what to improve next.

More job scrapers by the same author