eFinancialCareers Real-Time Data

Free trial: free Apify plans get 2 results per run. Upgrade to a paid plan for unlimited exports.

Live finance job intelligence from eFinancialCareers — the specialist hiring marketplace for banking, markets, asset management, fintech, and professional services. Search live roles by keyword and location, open full job records, track what named employers are hiring for, or turn any site URL into structured rows. Every record streams to your dataset in real time, with optional webhooks for instant alerts.

Who is it for

• Recruiters & sourcing teams building finance talent pipelines (analysts, quants, developers, compliance, bankers)
• Hiring managers & HR benchmarking live demand, titles, and advertised compensation
• Agencies & RPOs monitoring new mandates the moment they go live
• Job boards & career platforms enriching finance listings with structured detail
• Researchers & analysts tracking hiring trends across banks, funds, and fintechs
• AI agents & automation builders feeding fresh finance job data into CRMs, alerts, and reports

Features

Checkbox	What you get
🔍 Job Search (default on)	Live keyword search with location, e.g. analyst in London. Fast cards by default; toggle Enrich with full job details to merge the full description into the same row (detailsFetched: true)
📦 Job Details	Full record for specific jobs by numeric ID or URL — description, salary, location, type, company
🏢 Company Jobs	Hiring activity for named employers, e.g. Citi, Goldman Sachs
🔗 Scrape By URL	Any eFinancialCareers job or search-results URL, auto-detected
🔔 Delivery	Optional webhook (json or slack) pushed per record, in addition to the dataset
🌐 Connection	Residential proxy recommended; match the country to your market (GB/US)

Every discovered job is always saved — enriching never drops rows, and search enrichment never creates duplicate rows.

Input reference

• country (select, default GB): GB = United Kingdom market, US = United States market.
• enableJobSearch (default true), jobKeywords (default ["analyst", "compliance"]), jobTitle (optional extra title search), jobLocation (default London; empty = nationwide), jobsPerQuery (1–200, default 10), fetchJobDetails (default false).
• enableJobDetails, jobIds (numeric IDs, e.g. 24889625), jobUrls (detail URLs).
• enableCompanyJobs, companyNames (e.g. ["Citi"]), jobsPerCompany (1–200, default 10).
• enableScrapeByUrl, scrapeUrls.
• webhookUrl, webhookFormat (json | slack).
• proxyConfiguration (Residential default, country matched to country).

Empty input still runs a useful demo: Job Search for analyst + compliance in London (10 per keyword).

Output fields

One row per job. featureType is job_search, job_details, company_jobs, or scrape_by_url. Core fields: job_id, job_url, title, company, company_url, location, salary, job_type, industry, snippet, description_text, description_html, posted_date, apply_url, search_keyword / company_query, position, detailsFetched, pageType (URL scrapes), scrapedAt, url. Filter dataset views by featureType.

Webhooks

Set webhookUrl to receive each record as it is saved (dataset writes always happen too).

• json: the full record object — ideal for Zapier, Make, n8n, or your own hiring bot.
• slack: a Slack message payload ({ "text": "…" }) — paste an Incoming Webhook URL and jobs arrive as chat messages.

Delivery is best-effort: a failed webhook never stops the run or the dataset write.

MCP / AI-agent usage

Pair this actor with the Apify MCP server: your agent can start runs and read the dataset without custom code.

Example question for your agent:

“Use the eFinancialCareers actor to find live compliance jobs in London, then summarize the top 5 by company with salary and posting link.”

FAQ

• Which proxy should I use? Residential, with the country matched to your market (GB for the UK market, US for the US market).
• How does the free trial work? Free Apify plans receive up to 2 results per run with an upgrade notice. Paid plans are uncapped.
• How fresh is the data? Every run reads the live marketplace, so results reflect what candidates see right now — including roles posted minutes ago.
• Do full details slow down search? Enrichment adds a little extra time per record to merge the full description into the same row. Leave it off for the fastest scans.
• Search vs Details rows? job_search rows come from keyword discovery (enriched in place when the toggle is on). job_details rows come only from the Job Details feature for IDs/URLs you name.