…
", "searchQuery": "registered nurse", "detailFetched": true, "scrapedAt": "2026-08-04T09:28:41.112Z" } ``` #### Key output fields | Group | Fields | |---|---| | Identity | `jobId` (stable eluta hex id), `atsJobId`, `elutaUrl` | | Role | `title`, `employmentType`, `industry`, `descriptionText`, `descriptionHtml`, `descriptionSnippet` | | Salary | `salaryText`, `salaryMin`, `salaryMax`, `salaryCurrency` (CAD), `salaryType` (`YEAR` / `HOUR`) | | Employer | `companyName`, `companyLegalName`, `companySlug`, `companyUrl`, `companyWebsite`, `companyDomain`, `companyDescription`, `companyLogoUrl`, `naicsCode`, `companyHeadquarters` (address + lat/lng) | | Recognition | `topEmployer`, `topEmployerRating`, `topEmployerReviewUrl` (Canada's Top 100 Employers) | | Location | `location`, `addressLocality`, `addressRegion`, `addressCountry` | | Dates | `postedAgo`, `postedDate` (ISO), `closingDate` (ISO) | | Apply | `applyUrl` (real ATS link), `applyUrlResolved`, `sourceDomain` | | Run context | `searchQuery`, `searchUrl`, `isSponsored`, `detailFetched`, `scrapedAt` | ### How it works 1. Your keywords × locations become eluta searches (or your pasted URLs are auto-classified: SERP / SEO page / employer page / direct job). 2. SERP pages are walked via `?pg=N`, ~10 jobs per page, streaming rows into a sliding-window worker pool — first results arrive within seconds. 3. Each job's detail page is fetched and parsed: eluta renders two page variants (microdata and JSON-LD) and both are handled, with the full description, ISO dates, employer metadata and structured salary. 4. The outbound apply redirect (`/direct/i`) is resolved to the employer's real ATS URL. 5. The merged row is pushed to the dataset — one row per job, JSON/CSV/Excel export. ### What makes this different from other Eluta actors - **Apply links that actually apply.** Other actors return the eluta.ca job URL as `applyUrl`. This one resolves the redirect to the employer's ATS posting (e.g. `careersen-hrrh.icims.com/jobs/23804/...`). - **Full description coverage.** Both eluta page variants are parsed, so descriptions come back complete — including postings where SERP-only scrapers return empty text. - **Employer depth.** NAICS code, HQ address with coordinates, employer website/domain/logo/description, and Top-100 employer ratings — fields for lead-gen and market analysis, not just job listings. - **Honest rate-limit handling.** Eluta soft-blocks bursty IPs; this actor detects it and rotates through a residential pool automatically instead of silently returning truncated results. - **Real contact discovery, not description regex.** Other actors "extract emails" by pattern-matching the posting text — which contains no email for the vast majority of jobs. Opt-in `enrichEmails` discovers the hiring employer's actual contact emails from their website and public sources, and bills only per email actually found. ### Notes & limitations - **Salary coverage follows the source.** Only a minority of Canadian employers publish pay on their postings (~20–30% in our tests). Where eluta has it, you get structured min/max; where it only appears in prose, the text parser picks it up best-effort. - `applyUrl` falls back to the eluta job URL when the redirect can't be resolved (`applyUrlResolved: false`) — rare (≥85% resolve in testing). - `topEmployerRating` only exists for employers recognised in Canada's Top 100 Employers project (eluta is run by its publisher, Mediacorp). - Monitoring mode's first run returns everything matching — that seeds your baseline; subsequent runs return only new postings. - Sponsored SERP slots are included and flagged via `isSponsored`. ### FAQ **How fresh are the postings?** Eluta indexes employer career sites continuously — with `sortBy: date` the top results are typically minutes to hours old, and each row carries `postedAgo` + an ISO `postedDate`. **Can I scrape a specific employer's jobs?** Yes — paste their eluta employer page (e.g. `https://www.eluta.ca/jobs-at-sunnybrook`) into `startUrls`. **What does a "real apply URL" mean exactly?** Eluta's apply buttons go through an internal redirect. The actor follows that redirect server-side and stores the destination — the employer's own ATS posting — in `applyUrl`, with the source career-site domain in `sourceDomain`. **Does it cover all of Canada?** Yes. Leave `location` empty to search nationally, or run multiple cities in one go — every query × location pair becomes its own search in the same run. **How do I get only new jobs each day?** Enable `monitoringMode`, set `sortBy: date`, and schedule the actor daily. Already-delivered job IDs are skipped without fetching (and without charge). `resetMonitoringState` rebuilds the baseline. ### Support - **Bugs / feature requests** — open an issue on the GitHub repo - **Custom exports / tailored fields** — drop a note via the Apify Store contact form - **Other actors** — see my Apify Store profile for the rest of the catalog ### 🔎 Explore more scrapers Same engine, other job boards: - [TotalJobs Scraper](https://apify.com/memo23/totaljobs-scraper) — UK all sectors - [IrishJobs.ie Scraper](https://apify.com/memo23/irishjobs-scraper) — Ireland's leading job board - [StepStone Job Scraper](https://apify.com/memo23/stepstone-search-cheerio-ppr) — Germany, Austria, France, Denmark - [s1jobs Scraper](https://apify.com/memo23/s1jobs-scraper) — Scotland - [CWJobs Scraper](https://apify.com/memo23/cwjobs-scraper) — UK tech & IT …plus 100+ more on the [memo23 profile](https://apify.com/memo23). *** ### 🤖 For AI Agents & LLM Apps Compact reference for AI agents calling this actor via the [Apify MCP server](https://mcp.apify.com) or the Apify API (actor: `memo23/eluta-scraper`). **Purpose:** Turn eluta.ca keyword × location searches (or any eluta.ca URL) into structured Canadian job rows with CAD salary, employer metadata, and the employer's real ATS apply link. **Minimal input:** ```json { "query": ["software engineer"], "location": ["Toronto"], "maxItems": 20 } ``` Instead of keyword search you can pass `startUrls` — any eluta.ca URL (`/search?q=…`, SEO pages like `/Nurse-jobs-in-Toronto-ON`, employer pages `/jobs-at-…`, or direct `/spl/…` job URLs) is auto-classified. **Output:** one row per job — `jobId`, `atsJobId`, `title`, `companyName`, `companySlug`, `companyUrl`, `companyWebsite`, `companyDomain`, `naicsCode`, `companyHeadquarters` {streetAddress, addressLocality, addressRegion, postalCode, addressCountry, latitude, longitude}, `topEmployer`, `topEmployerRating`, `location`, `postedAgo`, `postedDate`, `closingDate`, `employmentType`, `industry`, `salaryText`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryType`, `sourceDomain`, `elutaUrl`, `applyUrl`, `applyUrlResolved`, `descriptionText`, `descriptionHtml`, `searchQuery`, `detailFetched`, `scrapedAt`. **Behaviors an agent should know:** - Always set `maxItems` — uncapped it defaults to 1000 across all searches. - `startUrls` are crawled instead of (or alongside) keyword searches; each `query` × `location` pair becomes its own search. - `includeDetails` and `resolveApplyUrls` default true (one extra request per job each); set both false for fast SERP-only rows. - `incrementalMode` (preferred) or legacy `monitoringMode` keep a per-search baseline in the key-value store and emit only NEW/UPDATED/REAPPEARED jobs — billed only for what changed. - Billing: $0.005 per run + $0.001 per result ($1 per 1,000 jobs); `enrichEmails` is billed per contact email actually found, never for misses. - Public postings only — salary is published on a minority of Canadian jobs, so salary fields are often null. *** ### ⚠️ Disclaimer This Actor is an independent tool and is **not affiliated with, endorsed by, or sponsored by** Eluta.ca, Mediacorp Canada Inc., or any of their subsidiaries or affiliates. All trademarks mentioned are the property of their respective owners. The scraper accesses only **publicly visible** job postings rendered server-side by eluta.ca — no login, no CAPTCHA solving, no authenticated endpoints. When eluta rate-limits an IP it backs off and rotates rather than attempting to bypass the verification page. Users are responsible for: - Complying with Eluta.ca's Terms of Service - Following PIPEDA and your jurisdiction's data-protection laws (GDPR, CCPA, etc.) when storing, processing, or republishing scraped postings - Not republishing scraped data in a way that competes commercially with Eluta.ca *** ### SEO Keywords eluta scraper, scrape eluta.ca, eluta api, eluta.ca job scraper, Apify eluta, canada job scraper, canadian jobs api, canada job listings data, toronto jobs scraper, vancouver jobs scraper, canadian salary data, job postings canada api, canada hiring data, recruitment data canada, job market analytics canada, canada's top 100 employers data, naics job data, employer career site scraper, ats apply links, job feed canada, job monitoring alerts canada, indeed canada alternative, job bank canada alternative # Actor input Schema ## `query` (type: `array`): Job search keywords — each entry runs as its own eluta search. Eluta in-query qualifiers (e.g. `nurse sort:post`) are allowed. ## `location` (type: `array`): City or region filters, e.g. `Toronto` or `Vancouver, BC`. Combined with every keyword. Leave empty to search all of Canada. ## `sortBy` (type: `string`): Result ordering on the eluta side. `date` surfaces the newest postings first (recommended for monitoring), `relevance` is eluta's default ranking. ## `startUrls` (type: `array`): Full eluta.ca URLs to crawl instead of (or in addition to) keyword searches. Supported: `/search?q=...`, SEO pages like `/Nurse-jobs-in-Toronto-ON`, employer pages like `/jobs-at-sunnybrook`, and direct job URLs (`/spl/...`). ## `includeDetails` (type: `boolean`): Fetch each job's detail page for the full description (HTML + text), ISO posted/expiry dates, employment type, industry + NAICS code, employer website, logo, HQ address with latitude/longitude, and the Canada's-Top-100 employer rating. Disable for fast SERP-only rows. ## `resolveApplyUrls` (type: `boolean`): Follow eluta's outbound redirect to capture the employer's real apply URL (e.g. `sunnybrook.talcura.com/...JobId=12800`) instead of just the eluta.ca job page. One extra lightweight request per job. ## `enrichEmails` (type: `boolean`): If enabled, tries to find a contact email for each hiring employer. The employer website usually comes straight from the job page's own metadata, and its contact/about pages are scanned for an email. Adds contactEmail + contactWebsite columns plus a detailed emailEnrichment object. Best-effort, billed per contact email found; only charged when an email is returned, never for misses. ## `qualifyByPayment` (type: `boolean`): Requires "Enrich with contact emails". Scans each employer's website — reusing the pages already fetched for email discovery, so no extra cost or time — for payment processors and e-commerce platforms (Stripe, Shopify, PayPal, Paddle, Lemon Squeezy, WooCommerce, Square, Chargebee and more). Adds takesPayments, paymentProcessors, stripeLiveKey and paymentConfidence. No extra charge — included with each enriched employer. ## `includeKeywords` (type: `array`): Only keep jobs whose title, company or description contains at least one of these (case-insensitive). Filtered rows are never charged. ## `excludeKeywords` (type: `array`): Drop jobs whose title, company or description contains any of these (case-insensitive). ## `fromDate` (type: `string`): Only keep jobs posted on or after this date (ISO 8601, e.g. 2026-08-01). ## `toDate` (type: `string`): Only keep jobs posted on or before this date (ISO 8601). A date-only value means through the end of that day. ## `maxAgeMinutes` (type: `integer`): Only keep jobs posted within the last N minutes. Empty or 0 = no age limit. Ideal for tight scheduled runs. ## `incrementalMode` (type: `boolean`): Compare against the previous run and only emit jobs that are NEW, UPDATED, or REAPPEARED — you are only charged for what changed. The first run seeds the baseline. Each emitted row carries `changeType` and `firstSeenAt`. ## `stateKey` (type: `string`): Optional stable name for this tracked search (e.g. "nurse-toronto"). Leave empty to auto-derive one from the search inputs — same inputs, same baseline. ## `emitUnchanged` (type: `boolean`): When incremental, also emit rows whose content did not change (charged as normal results). ## `emitExpired` (type: `boolean`): When incremental, emit a small `changeType: EXPIRED` row for every previously-tracked job that vanished from eluta. ## `skipReposts` (type: `boolean`): When incremental, skip jobs whose content matches a previously-expired posting (employer re-listed the same ad under a new id). ## `resetIncrementalState` (type: `boolean`): One-shot: drop the stored baseline for this state key at the start of the run. ## `monitoringMode` (type: `boolean`): Legacy id-only monitoring: jobs whose eluta ID was already delivered to you are skipped before the detail fetch (no charge). Kept for existing scheduled tasks — new setups should use Incremental mode above, which also detects UPDATED / REAPPEARED / EXPIRED and powers change-only notifications. ## `resetMonitoringState` (type: `boolean`): One-shot toggle: clear the legacy 'jobs already seen' record at the start of this run. Has no effect when legacy monitoring mode is off. ## `compact` (type: `boolean`): Emit only the core fields (id, title, company, location, salary, apply link, dates) — small payloads for AI-agent / MCP / LLM pipelines. ## `excludeEmptyFields` (type: `boolean`): Drop null / empty-string / empty-array fields from each record. ## `descriptionMaxLength` (type: `integer`): Truncate description fields to this many characters (0 = full text). Controls LLM prompt cost and dataset size. ## `telegramBotToken` (type: `string`): Your bot's token from @BotFather. With Chat ID set, a summary of new jobs is sent after each run. ## `telegramChatId` (type: `string`): Chat or channel id the bot posts to (e.g. "-1001234567890"). ## `slackWebhookUrl` (type: `string`): Slack incoming-webhook URL (api.slack.com/messaging/webhooks). ## `discordWebhookUrl` (type: `string`): Discord incoming-webhook URL (Server Settings → Integrations → Webhooks). ## `whatsappAccessToken` (type: `string`): WhatsApp Cloud API token (Meta Business system user). The recipient must have messaged your business number within the last 24h — Cloud API rule. ## `whatsappPhoneNumberId` (type: `string`): Your WhatsApp Business phone-number id (numeric, from the Meta dashboard). ## `whatsappTo` (type: `string`): Recipient phone in E.164 without + (e.g. "14165551234"). ## `webhookUrl` (type: `string`): Receives one JSON POST with { metadata, items } after the run — the universal escape hatch for n8n / Make / Zapier / custom backends. ## `webhookHeaders` (type: `object`): Optional custom headers for the generic webhook (e.g. {"Authorization": "Bearer …"}). ## `notificationLimit` (type: `integer`): How many job lines each chat notification includes (1–20). The rest are summarised as a count. ## `notifyOnlyChanges` (type: `boolean`): With Incremental mode on, notify only about NEW / UPDATED / REAPPEARED jobs. ## `maxItems` (type: `integer`): Hard cap on the number of jobs collected across all searches. Use this to limit billing. ## `maxPagesPerSearch` (type: `integer`): Stop paginating each search after this many result pages (~10 jobs per page). The walk also stops automatically when a page returns no new jobs. ## `maxConcurrency` (type: `integer`): Maximum number of job pages processed in parallel. ## `minConcurrency` (type: `integer`): Minimum number of job pages processed in parallel. ## `maxRequestRetries` (type: `integer`): Number of retries before a failed request is given up. ## Actor input object example ```json { "query": [ "software engineer" ], "location": [ "Toronto" ], "sortBy": "relevance", "includeDetails": true, "resolveApplyUrls": true, "enrichEmails": false, "qualifyByPayment": false, "incrementalMode": false, "emitUnchanged": false, "emitExpired": false, "skipReposts": false, "resetIncrementalState": false, "monitoringMode": false, "resetMonitoringState": false, "compact": false, "excludeEmptyFields": false, "notificationLimit": 5, "notifyOnlyChanges": false, "maxItems": 1000, "maxPagesPerSearch": 20, "maxConcurrency": 10, "minConcurrency": 1, "maxRequestRetries": 5 } ``` # 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 '