InfoJobs Scraper — Ofertas de Trabajo y Empleo España

Claude / Codex skill to describe and setup this actor: SKILL.md

Scrape current ofertas de trabajo y empleo from InfoJobs.net with keyword and province filtering. The shared flat output has no structured salary or AI skill columns.

What InfoJobs data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

Transparent posting dates: InfoJobs shows only relative Spanish text (Hace 2h, Hace 6d). We keep that text verbatim in postedAtText and expose the computed ISO date in postedAt — unparseable dates are never silently dropped, so you can always audit how each date was derived.

How to scrape InfoJobs with this Actor

1. Click Try for free / Run — no login to the target site, no cookies, no proxies to configure.
2. Adjust the input (keyword, filters, maxItems) or keep the defaults.
3. Run it and export the dataset as JSON, CSV or Excel, or read it over the API.

Run it from your own code:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/infojobs-scraper").call(run_input={"maxItems": 50})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], "—", item["company"], item["url"])

Or a single HTTP call that runs the Actor and returns items in one response:

curl -X POST \
  "https://api.apify.com/v2/acts/nomad-agent~infojobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxItems": 50}'

Input

Field	Type	Default	Notes
keyword	string	""	Free-text search query (e.g. "data engineer", "marketing"). Leave empty to return the latest postings across all categories.
province	string (select)	""	Restrict results to a single Spanish province (e.g. Madrid, Barcelona). Leave as "All provinces" to search nationwide.
teleworking	string	""	Keep only Presencial, Híbrido or Teletrabajo listings (accent/case-insensitive match on the card's work-mode label).
contractType	string	""	Keep only listings matching a contract-type label (Indefinido, De duración determinada, Fijo discontinuo, …).
workday	string	""	Keep only listings matching a jornada label (Completa, Parcial, Intensiva, Indiferente).
postedWithin	string	any	Keep only jobs published inside this window. Use any for no date filter, or a duration — 1h, 24h, 3d, 2w, 6m. Jobs the source published no date for are kept rather than dropped. InfoJobs shows posting dates as relative Spanish text (e.g. Hace 6d), which is parsed into an approximate age. The original text stays in postedAtText. Replaces postedSince, still accepted for existing integrations.
titleExclude	array of strings	[]	Skip listings whose title contains any of these case-insensitive terms.
companyExclude	array of strings	[]	Skip listings whose company name contains any of these case-insensitive terms.
maxItems	integer	15	Maximum number of postings to return. InfoJobs returns roughly 10–15 cards per page; set 0 for no additional cap.
timeoutSecs	integer	25	How long to wait for InfoJobs to respond before giving up, in seconds. (Advanced)
browserRendering	boolean	false	Use Chromium for listing pages. The Store prefill enables it for the most resilient first run; direct HTTP still falls back to Chromium when blocked. (Advanced)
residentialProxyFallback	boolean	false	After direct HTTP and ordinary Chromium both fail, try one HTTP-only listing request through Apify Residential Proxy in Spain. Paid proxy bandwidth applies. (Advanced)
cacheTtlSeconds	integer	1800	Reuses the last fetch for this many seconds so rapid re-runs don't hit InfoJobs again. Set 0 to always fetch live. (Advanced)

Freshness filtering (postedWithin)

InfoJobs shows posting dates as relative Spanish text on the search page, not an ISO date — typically a compact badge like "Hace 14m" (minutes), "Hace 2h" (hours) or "Hace 6d" (days), occasionally a spelled-out form like "Hace 2 semanas" or "Hace 3 meses". This text is parsed into an approximate age in days both to evaluate postedWithin and to compute the ISO postedAt field in the output; the original, unmodified text is always kept in postedAtText. Listings whose date text doesn't match a known pattern are always kept by the postedWithin filter, since their age can't be judged — postedAt is null for those.

Output example

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
  "schemaVersion": "nomad-agent-job-row-v1",
  "recordType": "posting",
  "source": "infojobs",
  "id": "a1b2c3",
  "url": "https://example.com/infojobs/jobs/a1b2c3",
  "title": "Senior Backend Engineer",
  "company": "Example Company",
  "locations": [
    "Bilbao",
    "Spain"
  ],
  "postedAt": "2026-09-02T00:00:00Z",
  "deadline": null,
  "description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
  "descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
  "workType": "remote",
  "custom": {
    "schemaId": "nomad-agent-job-custom-infojobs-v1",
    "data": {
      "postedAtText": "…"
    }
  }
}

Field	Meaning
schemaVersion	Always "nomad-agent-job-row-v1".
recordType	"posting" for a job, "diagnostic" for a row reporting something about the run itself.
source	Which job source the posting came from, from the collector registry's vocabulary — not the Actor name.
id	Stable identifier for the posting within source.
url	Canonical public URL of the posting on the source site.
title	Job title exactly as the source publishes it, untruncated.
company	Employer name as published.
locations	Places the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAt	When the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadline	Closing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
description	The complete posting body as plain text — never truncated, never summarised.
descriptionHtml	The posting body as the source's own markup, preserving lists, headings and links.
workType	Working arrangement: "remote", "hybrid" or "onsite".
custom	Facts only this source publishes, as {"schemaId", "data"}.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Integrations

Export results as JSON, CSV or Excel; connect via Make, Zapier or n8n; call directly with run-sync-get-dataset-items; or plug into AI agents through the Apify MCP server.

Pricing

Pay per event: $0.005 per Actor start and $0.0025 per job returned (less on higher Apify plans). 100 jobs ≈ $0.26. No subscription, no rental — you pay only for what you fetch.

The optional Residential proxy fallback is billed separately by Apify for bandwidth. It is off by default, runs only after both unproxied methods fail, and is limited to four listing-page requests, 4 MiB per response, and 16 MiB per run. It never proxies Chromium assets, detail pages, or CAPTCHA interaction.

Use cases

• Spanish job boards and alert bots (empleo en España)
• Recruiting agencies sourcing Spain-based talent
• Salary benchmarking for the Spanish market
• Regional labour-market dashboards

FAQ

Is it legal to scrape InfoJobs? This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case.

Do I need an account on the target site? No. Postings are fetched from public pages/APIs — no login, cookies or session tokens.

How fresh is the data? Every run fetches live listings. Results are cached for cacheTtlSeconds (default 30 min, set 0 to always hit the source live).

How many jobs can I get? maxItems caps the run (set 0 where supported for no cap). Most sources paginate from newest to oldest.

Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and reliability fixes ship fast.

Is this Actor useful to you? A short review on the Actor's Reviews tab helps other users find it — it takes a minute and is genuinely appreciated.

Related Actors

• Europe Jobs Scraper — 14 Sources in One
• Web Developer Jobs Scraper — 10 Boards in One
• Tecnoempleo Scraper — Spain IT & Tech Jobs
• EURES Job Scraper — EU Job Mobility Portal

---

From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.