IrishJobs Ireland Vacancy Listings Scraper
Pricing
from $0.71 / 1,000 item extracteds
IrishJobs Ireland Vacancy Listings Scraper
Export public IrishJobs Ireland vacancy listings with job IDs, employers, locations, advertised salary text and posting timestamps. Use keyword/location searches or IrishJobs search URLs for recurring recruitment snapshots.
Pricing
from $0.71 / 1,000 item extracteds
Rating
0.0
(0)
Developer
Automation Lab
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
Export IrishJobs Ireland vacancy listings as a clean recruitment snapshot. Give the Actor a keyword and optional location, or paste public IrishJobs.ie search URLs. Get job IDs, titles, employers, locations, advertised salary text, posting timestamps and vacancy links in JSON, CSV or Excel through Apify's dataset exports.
This is a listing-only product for recruiters, recruitment analysts and data teams who need repeatable observations of current vacancies. It does not collect applicant records, infer salaries or open individual job detail pages.
Why use this Actor?
- Join snapshots using stable source job IDs rather than job titles.
- Preserve salary wording, including “Not Disclosed”, without inventing ranges.
- Keep the search URL and observation time on every row for provenance.
- Deduplicate jobs within a run, including overlapping search pages.
- Use a lightweight public search route without supplying cookies, accounts or proxy credentials.
Scheduling and downstream comparison are possible with Apify tools. The Actor itself does not maintain historical state, detect changes or send alerts.
Who is it for?
Recruiters can refresh a shortlist of advertised roles. Labor-market analysts can compare vacancy snapshots over time. Data engineers can load the default dataset into a spreadsheet, warehouse or recruiting research pipeline.
Search results follow IrishJobs' own matching and ranking, including related roles and nearby locations. A keyword is not an exact-phrase filter and is not guaranteed to appear in every title.
Getting started
- Keep the default software-developer search, or enter your keyword.
- Optionally enter a location such as Dublin with the keyword.
- Set a small
maxItemsvalue for your first run. - Run the Actor and inspect Output → Vacancy records.
- Export the dataset as JSON, CSV or Excel.
Example keyword input:
{"keyword": "software developer","location": "Dublin","maxItems": 25,"maxPages": 2}
Alternatively, preserve a search you configured on the website:
{"startUrls": [{"url": "https://www.irishjobs.ie/jobs/software-developer"}],"maxItems": 30,"maxPages": 2}
Use either URL input or keyword/location input, never both. Only HTTPS search URLs on www.irishjobs.ie under /jobs are supported. Job-detail URLs, other domains and unsupported input fields fail validation.
Inputs and search behavior
| Input | Default | Meaning |
|---|---|---|
startUrls | Not set | 1–10 search URL objects; source query filters and starting page are preserved. |
keyword | Software developer when no search is supplied | Trimmed search text converted to an IrishJobs URL slug; upstream matching, not local substring filtering. |
location | Not set | Upstream location search; requires keyword. |
maxItems | 20 | Global cap of 1–250 unique saved jobs across all searches. Zero is invalid. |
maxPages | 2 | Global cap of 1–10 successful search pages, including the initial pages. |
maxRequestRetries | 1 | 0–2 additional attempts per page for transient HTTP/network failures. |
Both caps apply together. Ten pages normally cover up to 250 source rows, but fewer unique jobs may be returned. Repeated records consume a page without producing duplicate output. Search URLs run in the supplied order; an early search can consume the entire limit before later searches begin.
There is no unlimited mode. Source exhaustion, billing limits and the run timeout can stop collection before the requested cap. Apify schedules can repeat a saved input, but each run is an independent snapshot.
Extracted data
| Field | Meaning |
|---|---|
jobId | Stable numeric source ID stored as text. |
title | Public vacancy title. |
employer | Source employer or advertiser name, nullable. |
location | Source location text, nullable; no independent geocoding. |
salaryText | Advertised wording, including “Not Disclosed”, or null when absent. |
postedText | Relative posted wording only if supplied; normally null on this route. |
postedAt | Source datePosted timestamp, nullable and unmodified. |
jobUrl | Public vacancy URL without query or fragment. |
sourceSearchUrl | Search URL that supplied the row, including pagination. |
fetchedAt | UTC observation timestamp. |
The API currently supplies posting timestamps rather than relative “days ago” text. The Actor does not calculate a replacement for missing posted text. Salary fields are not estimates or verified compensation offers.
Output example
A representative public search record has this shape; the observation timestamp varies:
{"jobId": "108110284","title": "Full Stack Software Developer Lead","employer": "PM Group","location": "Dublin, County Dublin","salaryText": "€ Not Disclosed","postedText": null,"postedAt": "2026-10-07T20:21:48.9Z","jobUrl": "https://www.irishjobs.ie/job/full-stack-lead/pm-group-job108110284","sourceSearchUrl": "https://www.irishjobs.ie/jobs/software-developer","fetchedAt": "2026-10-16T10:00:00.000Z"}
All primary records go to the run's default dataset. No global shared dataset is reused, and no raw HTML or debugging objects are emitted as results.
How much does it cost to export IrishJobs vacancy listings?
The Actor charges once for start, then once per unique vacancy saved through item. Duplicate records, unsuccessful pages and empty pages have no item charge. A valid search with no results still has a start charge.
The run start costs $0.001. Per-vacancy prices are FREE $0.001357, BRONZE $0.00118, SILVER $0.0009204, and GOLD / PLATINUM / DIAMOND $0.000708. These prices include the Actor's required infrastructure; there is no undisclosed third-party fee.
| Unique vacancies | BRONZE estimated total including start |
|---|---|
| 1 | $0.00218 |
| 25 | $0.03050 |
| 100 | $0.11900 |
Spend tiers depend on qualifying aggregate monthly Apify Store spend, not volume in this Actor alone. Other tiers can have different unit prices. The pricing tab is authoritative; estimates are not guaranteed invoices. No additional source account, paid source API, browser or residential-proxy subscription is required. There is no separate detail-page charge because details are not fetched.
Limits and failure behavior
This Actor exports current public listings only. It does not promise full descriptions, application endpoints, employer profiles, contact emails, historical completeness, private applicant data, inferred salaries or other job boards.
The public source can change, rate-limit requests or return a challenge. Challenge/invalid JSON and permanent HTTP failures are errors, not valid empty searches. Only transient network errors and selected temporary HTTP failures receive bounded backoff retries. No hidden browser or proxy fallback is enabled.
If a later page fails, the run fails and previously saved rows are partial, not a complete successful snapshot. Repeated pagination URLs or pages containing only already-seen jobs are reported rather than silently looping. Source order and job availability can change while pagination is running.
Integrations and recurring snapshots
- Google Sheets or Excel: export CSV and compare
jobIdacross observation dates. - n8n, Make or Zapier: start a run, wait for its terminal status, then read the returned default dataset.
- Warehouse pipelines: load dataset JSON and retain
sourceSearchUrlandfetchedAtas provenance columns. - Apify schedules: repeat the same search daily and compare downstream. A missing job in a capped snapshot does not prove a vacancy closed.
The Actor does not notify employers, submit applications, contact candidates or write to recruitment systems.
API usage
Keep your Apify token private. The following examples start a run; its response is run metadata, not the vacancy rows. Wait for success and then read defaultDatasetId.
cURL
curl -X POST \'https://api.apify.com/v2/acts/automation-lab~irishjobs-vacancy-listings-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"keyword":"software developer","maxItems":25,"maxPages":2}'
JavaScript
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/irishjobs-vacancy-listings-scraper').call({ keyword: 'software developer', maxItems: 25, maxPages: 2 });if (run.status !== 'SUCCEEDED') throw new Error(`Run ${run.id}: ${run.status}`);const { items } = await client.dataset(run.defaultDatasetId).listItems({ limit: 25 });console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('automation-lab/irishjobs-vacancy-listings-scraper').call(run_input={'keyword': 'software developer', 'maxItems': 25, 'maxPages': 2})if run['status'] != 'SUCCEEDED':raise RuntimeError(f"Run {run['id']}: {run['status']}")print(client.dataset(run['defaultDatasetId']).list_items(limit=25).items)
MCP: Claude Code, Claude Desktop, Cursor and VS Code
For Claude Code:
claude mcp add --transport http apify \"https://mcp.apify.com?tools=automation-lab/irishjobs-vacancy-listings-scraper"
For Claude Desktop, Cursor and VS Code, adapt the HTTP server configuration to the client's supported format and authenticate through its Apify setup:
{"mcpServers": {"apify": {"type": "http","url": "https://mcp.apify.com?tools=automation-lab/irishjobs-vacancy-listings-scraper"}}}
Example prompt: “Export 25 software-developer vacancies from IrishJobs Ireland and show titles, employers and salary wording.” Another: “Run a Dublin vacancy snapshot and give me the dataset link for downstream comparison.”
Discover the scoped tool names and argument schemas with tools/list; Actor selection also adds run/data tools and does not expose exactly one tool. For an authorized run, start once and retain its run ID and storage IDs. call-actor waits at most 45 seconds (default 30); configure client timeout above the chosen server wait plus transport margin.
If still running, check that same run with bounded 2/4/8-second backoff capped at 10 seconds, with a 120-second total deadline. After a client timeout recover the known run, never restart just to poll. At deadline report pending and its run ID. Terminal failures must be reported honestly, with any available rows labeled partial.
After success, fetch dataset items in pages of 20 using explicit offset, limit and only needed fields. Example consumer context budget: at most 100 source rows and 64 KiB serialized UTF-8 content, whichever comes first. Enforce bytes host-side before model injection; omit or summarize oversized rows with disclosure. If your client cannot intercept responses, do not claim a hard byte guarantee. Report returned count, next offset and truncation; keep full exports outside model context. These are consumer limits, not reductions in Actor collection. No universal token-saving claim is made.
Legality, responsible use and non-affiliation
Use public vacancy information responsibly, respect applicable source terms and privacy law, and assess your own intended downstream use. Public access does not grant unrestricted reuse rights. This independent tool is not affiliated with, endorsed by or certified by IrishJobs or its operator. Source names are used descriptively, not as company branding.
Apify's standard terms apply. No custom end-user contract is added. Do not use this product to gather applicant records or profile private individuals.
Privacy, retention and AI
The Actor processes public job advertisements and supplied search parameters. It does not use AI at runtime or send job data to an AI provider. An original generated icon is a static build asset, not a runtime data recipient.
Failed operations send sanitized diagnostic input, exceptions and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL query strings are removed; reports are retained for 30 days. Normal logs contain counts, statuses and bounded error messages rather than page bodies or credentials.
Apify stores input, dataset rows and run logs under your account's storage and retention settings. This Actor does not create an additional historical database or persist source cookies. Delete run datasets and key-value stores in Apify when no longer needed; deleting a run alone should not be assumed to delete all associated storage. Diagnostic retention is separate. Apify hosts execution/storage and the private diagnostic service receives scrubbed failures only.
FAQ and troubleshooting
Why is salary missing or “Not Disclosed”? The source did not advertise a salary. No value is inferred or filled from another website.
Why is postedText null? This route supplies postedAt; it normally has no relative wording. Use the source timestamp for analysis.
Why fewer records than requested? Check maxPages, upstream availability, deduplication, billing limits and timeout. Limits are caps, not promised counts.
Can I use a job-detail URL? No. Paste a /jobs/ search URL or use keyword/location. This Actor intentionally does not fetch full descriptions.
Why did a run fail after saving rows? An upstream error or pagination inconsistency occurred. Retain the run ID and treat those rows as partial; do not mistake a challenge page for no vacancies.
Can it detect new or closed roles? Not natively. Schedule snapshots and compare IDs downstream. Capped snapshots are not complete closure evidence.
Related Actors and support
For a separate country-specific recruiting workflow, see jobs.ch Switzerland Job Listings Scraper and Karriere.at Austria Job Listings Scraper. Their source coverage is separate and is not included in this Actor.
For help, open an issue on this Actor's Apify page with the run URL, sanitized input and expected versus observed behavior. Do not post credentials or private applicant data.