# CEE Jobs Feed: Greenhouse, Lever & Ashby, Visa & Relocation (`ayuki/cee-job-feed`) Actor

Live job feed for Latvia, Lithuania, Estonia, Poland, Czechia, Romania and other CEE countries from public Greenhouse, Lever and Ashby job boards. Remote, visa sponsorship and relocation tags, links to original postings.

- **URL**: https://apify.com/ayuki/cee-job-feed.md
- **Developed by:** [LV Data Tools](https://apify.com/ayuki) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## CEE Jobs Feed: Greenhouse, Lever & Ashby, Visa & Relocation

A live **job feed for Central and Eastern Europe**: Latvia, Lithuania, Estonia, Poland, Czechia, Slovakia, Hungary, Romania, Bulgaria, Croatia, Slovenia, Serbia, Ukraine and more. It reads employers' **public Greenhouse, Lever and Ashby job boards** and tags each job with **remote**, **visa sponsorship** and **relocation** flags detected from the posting text.

Use it to find tech, product and business roles in the Baltics and CEE, to find remote jobs open to Europe, or to see which employers mention visa sponsorship or relocation.

### Features

- **CEE country presets**: choose countries; locations are matched by country and major-city names (Riga, Vilnius, Tallinn, Warsaw, Kraków, Prague, Bucharest, Sofia…).
- **Remote jobs** open to Europe / EU / EMEA / worldwide (optional).
- **Visa sponsorship & relocation tags**: `yes` (offered), `no` (explicitly not offered) or `null` (not mentioned).
- **Your own boards**: add `greenhouse:slug`, `lever:slug`, `ashby:slug` or a board URL.
- **Built-in employer list**: about 30 companies with public boards that regularly hire in CEE (Veriff, Wolt, Bitpanda, JetBrains, Surfshark, Hostinger, Docplanner, Pipedrive, Omnisend, Ataccama, UiPath and others).
- **Lightweight output by default**: metadata, tags and a link to the original posting. Full description optional.

### Input

| Field | Description |
|---|---|
| `countries` | CEE ISO codes (default: all presets) |
| `includeRemote` | Include remote jobs open to Europe/EU/EMEA/worldwide (default true) |
| `boards` | Extra boards: `greenhouse:slug`, `lever:slug`, `ashby:slug` or URLs |
| `useSeedList` | Include the built-in employer list (default true) |
| `keywords` | Title keywords (any match) |
| `onlyVisaSponsorship` / `onlyRelocation` | Keep only tagged jobs |
| `postedWithinDays` | Age filter (jobs without a date are excluded when set) |
| `includeDescription` | Output full text (contacts removed); default false |
| `maxItems` | Default **100**; newest first |

```json
{"countries": ["LV", "LT", "EE"], "keywords": ["engineer", "developer"], "maxItems": 100}
```

### Output

```json
{
  "jobId": "ashby:surfshark:57ed79cb-878f-4499-8fdf-28b2f4f7b07c",
  "source": "ashby",
  "boardSlug": "surfshark",
  "company": "surfshark",
  "title": "Mobile Acquisition Specialist",
  "department": "Surfshark",
  "team": "Marketing",
  "employmentType": "FullTime",
  "workplaceType": "hybrid",
  "remote": true,
  "locations": ["Vilnius", "Warsaw", "Kaunas"],
  "countries": ["LT", "PL"],
  "visaSponsorship": null,
  "relocation": null,
  "tags": ["remote"],
  "salary": null,
  "postedAt": "2026-09-03T13:42:55Z",
  "updatedAt": null,
  "url": "https://jobs.ashbyhq.com/surfshark/57ed79cb-878f-4499-8fdf-28b2f4f7b07c",
  "applyUrl": "https://jobs.ashbyhq.com/surfshark/57ed79cb-878f-4499-8fdf-28b2f4f7b07c/application",
  "description": null,
  "attribution": "Job posting published by the employer on its public Ashby job board; link to the original posting included."
}
```

`RUN_STATS` records boards read, boards not found or failed, matches per country and tag counts.

### How tags work

Tags come from sentence-level keyword patterns over the posting text, e.g. "visa sponsorship available" → `yes`, "we are unable to sponsor visas for this role" or "must have the right to work" → `no`. They are best-effort hints: always check the original posting.

### Scope and terms

This is a **job feed**, not an analytics product about ATS vendors or their customers. It reads only public posting endpoints that the boards publish for embedding job listings. It never fetches application forms or questions and never submits applications. Postings belong to the employers; every record links to the original posting. Not affiliated with Greenhouse, Lever, Ashby or any employer. Unlisted Ashby postings are skipped.

### Personal data

Job postings describe roles, not people. Email addresses and phone numbers (for example a recruiter's contact details) are removed from all output, and the full description is off by default. Do not use the output to collect or enrich data about recruiters or other individuals.

### Privacy notice

Controller: **Artyom Kutnevskiy (trading as LV Data Tools), contact lvdatatools@gmail.com**. Version 0.1, 2026-10-15.

- **Data concerned:** job postings that employers publish on their public Greenhouse, Lever and Ashby job boards: job title, company, department/team, locations, workplace type, employment type, published salary range, dates and links. Postings are about roles, not people, but the text can incidentally contain a recruiter's or hiring manager's name or contact details.
- **Minimisation:** by default only posting metadata, detected tags (remote, visa sponsorship, relocation) and the link are output; the full description is output only if you enable `includeDescription`. Email addresses and phone numbers are removed from all output text. Application forms and application questions are never requested, and no candidate data is processed. Unlisted Ashby postings (`isListed` = false) are skipped. Names that appear inside free text cannot all be recognised automatically; any identified personal contact data must be removed.
- **Sources:** public job-board APIs: `boards-api.greenhouse.io`, `api.lever.co` / `api.eu.lever.co`, `api.ashbyhq.com` (posting API), for the boards you list plus a built-in list of employers. No login, API key or private endpoint is used.
- **Positioning:** this Actor is a job feed for job seekers, recruiters and labour-market research. It is not an analytics tool for ATS vendors, and it is not affiliated with Greenhouse, Lever, Ashby or the employers. Each record links to the employer's original posting; apply there.
- **Roles:** the publisher (LV Data Tools) is controller for the Actor's own source collection and minimisation, and acts as processor for each user's run output under §5.2 of the Apify Standard Actor Contract, while the user is controller of that output and its reuse.
- **Purpose:** discovery of open roles in Central and Eastern Europe and remote roles open to the region. No profiling of people, contact enrichment or automated decision-making about individuals.
- **Legal basis:** Art. 6(1)(f) GDPR (legitimate interest), with the minimisation above. Users must establish the basis for their own reuse.
- **Recipients:** the user running the Actor and recipients they choose. Apify Technologies s.r.o. provides the hosting platform. Datasets are not automatically sent to other parties by this Actor.
- **Retention:** LV Data Tools keeps no separate copy of output. Responses are processed in memory. Output datasets and `RUN_STATS` follow the user's Apify storage/retention settings. Logs contain counters only.
- **Transfers outside the EEA:** hosting may involve transfers depending on Apify's infrastructure; see [Apify's privacy policy](https://apify.com/privacy-policy).
- **Rights:** access, rectification, erasure, restriction, objection (Art. 21) and complaint to a supervisory authority, e.g. Latvia's Datu valsts inspekcija ([dvi.gov.lv](https://www.dvi.gov.lv/)) or your local authority. Requests concerning the Actor go to lvdatatools@gmail.com; for a user's exported dataset, contact that user as well. Employers can ask for their board to be removed from the built-in list.
- **Individual notification / Art. 14(5)(b) assessment (2026-10-15):** contact details are removed and no person records are kept; individuals appear only incidentally in postings their employer chose to publish. The publisher holds no contact details for them, and contacting them would require collecting more personal data. Individual notification would involve disproportionate effort; safeguards are this public notice, metadata-only default output, contact scrubbing and individual handling of objections.

### FAQ

**Can I add any company?** Yes, if it uses a public Greenhouse, Lever or Ashby board. Pass the board slug or URL.

**How fresh is it?** Live: boards are read during each run.

**Why do some jobs have no country?** They are remote roles open to Europe/EU/EMEA/worldwide (when `includeRemote` is on).

# Actor input Schema

## `countries` (type: `array`):

Jobs located in any of these countries (detected from posting locations).

## `includeRemote` (type: `boolean`):

Also return remote jobs whose location mentions Europe, EMEA, CEE, Baltics or worldwide (or no location).

## `boards` (type: `array`):

greenhouse:slug, lever:slug, ashby:slug or board URLs (e.g. https://jobs.ashbyhq.com/surfshark).

## `useSeedList` (type: `boolean`):

About 30 companies with public boards that regularly hire in Central & Eastern Europe.

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

Keep jobs whose title contains any keyword (case-insensitive).

## `onlyVisaSponsorship` (type: `boolean`):

Keep only postings whose text mentions visa sponsorship/support as offered (text detection, best effort).

## `onlyRelocation` (type: `boolean`):

Keep only postings whose text mentions relocation support (text detection, best effort).

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

0 or empty = any age.

## `includeDescription` (type: `boolean`):

Off by default. When on, the job text is included with emails and phone numbers removed.

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

Max results.

## Actor input object example

```json
{
  "countries": [
    "LV",
    "LT",
    "EE",
    "PL"
  ],
  "includeRemote": true,
  "boards": [
    "ashby:surfshark"
  ],
  "useSeedList": true,
  "onlyVisaSponsorship": false,
  "onlyRelocation": false,
  "includeDescription": false,
  "maxItems": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `stats` (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 = {
    "countries": [
        "LV",
        "LT",
        "EE",
        "PL"
    ],
    "boards": [
        "ashby:surfshark"
    ],
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("ayuki/cee-job-feed").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 = {
    "countries": [
        "LV",
        "LT",
        "EE",
        "PL",
    ],
    "boards": ["ashby:surfshark"],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("ayuki/cee-job-feed").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 '{
  "countries": [
    "LV",
    "LT",
    "EE",
    "PL"
  ],
  "boards": [
    "ashby:surfshark"
  ],
  "maxItems": 100
}' |
apify call ayuki/cee-job-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ayuki/cee-job-feed"
        }
    }
}
```

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/oA0PV8aJg0qEBWbXo/builds/K7SWRxhQZfAYFbLnm/openapi.json