# CV.ee Scraper: Estonia Jobs with Salary (`ceejobs/cv-ee-scraper`) Actor

Scrape CV.ee (Estonia) job listings into clean JSON: title, company, town, EUR salary normalized to monthly, posting and expiry date, tags, full ad text where the board publishes it. Pay per result, no subscription.

- **URL**: https://apify.com/ceejobs/cv-ee-scraper.md
- **Developed by:** [CEE Jobs](https://apify.com/ceejobs) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CV.ee Jobs Scraper — Estonia job listings with salary

Extract CV.ee job listings with salary, location and posting date for Estonia market
research, recruiting and lead generation.

### What you get

- Every job on www.cv.ee that matches your keywords, as one structured row each: title, company,
  location, employment type, posting date and the canonical job URL.
- The exact salary range the employer entered, in EUR — the only currency this board quotes —
  and the same range as gross **EUR per month** in `salary.minEurMonth` / `salary.maxEurMonth`.
  CV.ee publishes amounts rather than a printed label, so `salary.raw` is always `null`.
- The ad text wherever the board hosts it, plus the expiry date, the work type and the board's
  own category and skill tags — all of it read off the search results themselves, so no run
  ever has to open a second page per job.
- A stable `id` of the form `cv-ee:<board job id>`, so repeat runs deduplicate against
  your own database instead of against a row number.

### Sample item

```json
{
  "id": "cv-ee:1641665",
  "url": "https://www.cv.ee/et/vacancy/1641665",
  "title": "Java Developer",
  "company": "Playtech Estonia OÜ",
  "companyUrl": "https://www.cv.ee/et/search/employer/2410",
  "location": {
    "raw": "Tartu",
    "city": "Tartu",
    "country": "EE"
  },
  "remote": true,
  "employmentType": "FULL_TIME",
  "salary": {
    "min": 2970,
    "max": null,
    "currency": "EUR",
    "period": "month",
    "raw": null,
    "minEurMonth": 2970,
    "maxEurMonth": null
  },
  "postedAt": "2026-08-18",
  "expiresAt": "2026-09-17",
  "description": "Your influential mission. You will... Develop and maintain the automation fram…",
  "tags": [
    "INFORMATION_TECHNOLOGY",
    "Java",
    "spring"
  ],
  "source": {
    "board": "cv-ee",
    "boardJobId": "1641665",
    "scrapedAt": "2026-08-22T14:45:56.503Z"
  }
}
```

`description` is the ad's own text, with e-mail addresses, phone numbers and "Kontakts:" lines
stripped out — but only wherever the board hosts that text itself. A substantial minority of
ads publish none of it in the search results and ship `description: null` rather than a
truncated teaser. `tags` holds the board's own job category next to the skills the employer
tagged the ad with, spelling and all.

`remote` has three states, and `false` is not the same answer as `null`. It is `true` when CV.ee
marks the posting as fully remote work, `false` when the board marks it as hybrid or on-site,
and `null` when the posting says nothing about it at all. Filter on `remote === true` for
remote-only work, and do not read a missing flag as an office job.

`postedAt` is the board's publish date, which moves when an employer renews an ad — a renewed
posting reads as freshly posted, and `postedWithinDays` will keep it. Use `expiresAt` to tell
how much of the ad's run is left. Anything CV.ee did not publish is `null`, never missing.

### Input

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| `keywords` | array of strings | `[]` | One search per keyword (job title, skill, company). Empty runs the board's default listing. |
| `location` | string | `""` | City or region, in the board's own language. location is matched client-side against the town name behind the listing's town id (the board publishes ids, not names); accents are optional, so "parnu" finds Pärnu. |
| `maxItems` | integer | `100` | Hard stop after this many jobs. This is the cost dial. |
| `postedWithinDays` | integer | `0` | Keep only jobs posted in the last N days. `0` disables the filter. |
| `startUrls` | array | `[]` | Search URLs on www.cv.ee to crawl directly instead of building searches from `keywords` — the board's own `https://www.cv.ee/api/v1/vacancy-search-service/search?limit=20&offset=0&…`, with whatever filters you want on it. |
| `extra` | object | `{}` | Board-specific filters. This board takes no extra filters yet. |
| `proxyConfiguration` | object | Apify proxy | Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected. |

There is no `includeDetails` switch: the search results already carry the description, the
expiry date and the exact salary, so there is no detail page worth opening and no second
charge to opt into.

### Pricing

$2 per 1,000 jobs. No subscription, and no second charge for descriptions — this actor
never opens a detail page, so the `job-detail` event is never billed.

### Limitations

Public listing data only — no recruiter names or e-mail addresses, no data behind a login. The
crawler obeys www.cv.ee's `robots.txt`, including for URLs you pass in `startUrls`, and runs on
datacenter proxies without any CAPTCHA or challenge circumvention: a challenge page is reported
as an error, not retried through another browser. Apify datacenter proxy groups only; residential groups and custom
proxy URLs are rejected before the run starts. Rows come from CV.ee's own public search API —
the one the site's search page itself reads. A job filed under a town the board has not
published a name for keeps its country and ships with a `null` city. www.cv.ee's `robots.txt`
also carries `Content-Signal: ai-train=no`: this actor does not train anything on the rows it
returns, and neither should what you build on them.

# Actor input Schema

## `keywords` (type: `array`):

One search per keyword; on boards without server-side search the keywords filter the full listing client-side (see the actor README).

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

City or region in the board's own language (e.g. Bratislava, Praha, Warszawa). Optional.

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

Stop after this many jobs. Controls cost: $2 per 1,000 jobs.

## `postedWithinDays` (type: `integer`):

Only keep jobs posted in the last N days. 0 = no filter.

## `startUrls` (type: `array`):

Listing URLs from the board to crawl directly instead of keywords.

## `extra` (type: `object`):

See the README for the filters this board supports.

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

Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected. The datacenter pool is enough for this board.

## Actor input object example

```json
{
  "maxItems": 100,
  "postedWithinDays": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `jobsCsv` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("ceejobs/cv-ee-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 = { "proxyConfiguration": { "useApifyProxy": True } }

# Run the Actor and wait for it to finish
run = client.actor("ceejobs/cv-ee-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 '{
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call ceejobs/cv-ee-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ceejobs/cv-ee-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/OYVei5X6ee6nvNXph/builds/7yfK1Wb30wpZdCgIU/openapi.json