# eFinancialCareers Jobs Scraper (`scrapyx/efinancialcareers-jobs-scraper`) Actor

Scrapes finance and banking job listings from eFinancialCareers. Each row carries title, company, location, job type, salary and posted date, with optional full job description.

- **URL**: https://apify.com/scrapyx/efinancialcareers-jobs-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.84 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## eFinancialCareers Jobs Scraper

Scrapes finance and banking job listings from **eFinancialCareers**, the
leading job board for finance-industry roles. Each row carries title,
company, location, job type, salary and posted date, with optional full job
description.

***

### What each row contains

| Field | Notes |
| --- | --- |
| `title` | Job title |
| `company` | Employer name |
| `location` | City, country |
| `jobType` | Permanent, Contract, etc. |
| `salary` | Displayed value — often "Competitive" rather than a figure |
| `posted` | Relative date, e.g. "27 days ago" |
| `description` | Full job description (only with `includeJobDetails`) |
| `url` | Listing URL |

#### Record types

| `recordType` | One per | Purpose |
| --- | --- | --- |
| `SEARCH_SUMMARY` | query | upstream's own count, requests spent, honesty flags |
| `JOB` | listing | the listing itself |
| `ERROR` | failed input | so every input maps to at least one row |

***

### Search is relevance-based, not exact-match

`keyword` is full-text search across a ~70,000-job corpus, the way a search
engine works — not a closed category list. There is no "invalid keyword"
this Actor can detect, because essentially any finance-adjacent phrase
matches something. Search broadly and use `location` to narrow, rather than
expecting an exact-title lookup.

### The one real trap: an unresolved location silently drops the filter

An unrecognised location is not rejected — it silently falls back to the
worldwide result set, and the page's own displayed heading can even show an
unrelated, nonsensical placeholder string rather than an error. This Actor
detects the failure by comparing the result **count** against a
keyword-only baseline fetched once per query (the count is the reliable
signal; the displayed text is not) and reports `locationApplied: false`
with **zero rows** rather than quietly returning worldwide results labelled
as location-filtered.

***

### Input

| Field | Notes |
| --- | --- |
| `keyword` | Required. Free-text job title/skill search |
| `location` | Optional. City or country name |
| `queries` | Optional array to run several searches in one call |
| `includeJobDetails` | One extra request per listing, for the full description |
| `maxItems` | Per query |
| `minRequestInterval` | Defaults to 1s; raise to 10s to match robots.txt's stated crawl delay |

***

### Example

```json
{
  "keyword": "quant trader",
  "location": "singapore",
  "includeJobDetails": true,
  "maxItems": 100
}
```

### Known limits

- No unfiltered "browse all jobs" mode is offered — `keyword` is required.
- Salary is frequently "Competitive" rather than a figure; that is what
  upstream displays, passed through as-is.
- A small, constant set of sponsored listings (~5 of every 20) repeats
  across every page of a large result set — deduplicated automatically, so
  it never produces duplicate rows.

### Anti-bot

Mostly none — seven TLS fingerprints tested locally on both search and detail
pages returned clean data every time — but an occasional shared
block/maintenance page from eFinancialCareers' corporate parent (DHI Group)
does appear on some cloud requests. The Actor detects it by content (not just
status code, since it can arrive as a plain HTTP 200) and automatically
rotates fingerprint and exit IP to recover, which succeeded in verification.
Defaults to residential proxy, since cloud egress is fingerprinted
differently from a local test. `robots.txt`'s `/search` path is never used by
this Actor — it works entirely through the unrestricted `/jobs/{keyword}`
surface.

# Actor input Schema

## `keyword` (type: `string`):

e.g. `client account manager`, `quant trader`, `compliance officer`. This is full-text relevance search across eFinancialCareers' finance/banking job corpus, not an exact-title match — it will always return something plausible for reasonable finance-industry terms, the way a search engine does.

## `location` (type: `string`):

e.g. `hong kong`, `singapore`, `new york`, `london`. Leave empty to search worldwide.

An unrecognised location is not rejected upstream — it silently drops the filter (the page's own displayed location text can even show something unrelated and nonsensical). This Actor detects that by comparing the result count against the location-less baseline, and reports `locationApplied: false` with zero rows rather than returning an unfiltered result set labelled as filtered.

## `queries` (type: `array`):

Optional. Run several searches in one Actor call, each producing its own SEARCH_SUMMARY row. Each entry accepts `keyword`, `location`, `maxItems`, `includeJobDetails`. When set, the top-level fields above are ignored.

Example: `[{"keyword": "quant trader", "location": "singapore"}, {"keyword": "compliance officer", "location": "london"}]`

## `includeJobDetails` (type: `boolean`):

Search results already carry title, company, location, job type, salary and posted date. This fetches each listing's own page for the complete job description text — one extra request per listing.

## `maxItems` (type: `integer`):

Stop after this many jobs per query. Set to 0 for everything upstream will serve.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across all queries and detail fetches.

## `minRequestInterval` (type: `integer`):

Paces how often requests START, without tying up a concurrency slot. eFinancialCareers' own robots.txt states a 10-second crawl delay for general crawlers; this defaults to a lighter 1 second, but raise it to 10 for a fully compliant crawl on large jobs.

## `proxyConfiguration` (type: `object`):

Residential by default. No bot challenge appeared on any of the 7 TLS fingerprints tested across search and detail pages, but datacentre egress from a cloud platform is fingerprinted differently from a local test.

## Actor input object example

```json
{
  "keyword": "quant trader",
  "location": "",
  "queries": [],
  "includeJobDetails": false,
  "maxItems": 100,
  "maxConcurrency": 3,
  "minRequestInterval": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keyword": "quant trader"
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/efinancialcareers-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "keyword": "quant trader" }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/efinancialcareers-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keyword": "quant trader"
}' |
apify call scrapyx/efinancialcareers-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/efinancialcareers-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BfnmedgvEYJBuCMfY/builds/azPiZhG4MGZ7FZZ6F/openapi.json