---
name: eures-cross-border-job-search-and-vacancy-lookup
description: "Search EURES's cross-border EEA job vacancy index by keyword, country, region, sector, contract type, education level and more, or fetch full detail - salary, benefits, contacts - for specific vacancy IDs. Output fields: title, employerName, countries, positionScheduleCodes, positionOfferingCode and more, as JSON rows. Use it for requests like \"EURES Cross-Border job search\", or a CSV/JSON export of public EURES data."
---

# EURES Cross-Border Job Search & Vacancy Lookup

Search EURES's cross-border EEA job vacancy index by keyword, country, region, sector, contract type, education level and more, or fetch full detail - salary, benefits, contacts - for specific vacancy IDs.

- Actor: https://apify.com/vexaloom-labs/eures-cross-border-job-search-and-vacancy-lookup (ID `vexaloom-labs~eures-cross-border-job-search-and-vacancy-lookup`)
- n8n workflow for the same Actor: https://scraperfinder.com/n8n/eures-cross-border-job-search-and-vacancy-lookup/
- Example input: `references/example-input.json`
- Input schema: `references/input-schema.json`
- Output fields: `references/output-fields.json`

## When to use

Use this skill when the user wants:

- EURES Cross-Border job search
- a repeatable export of public EURES data as CSV or JSON

Do not use it for private, login-protected or paywalled data.

## What it returns

One JSON row per result. Columns from the Actor's dataset schema:

- `title`: Title
- `employerName`: Employer Name
- `countries`: Countries
- `positionScheduleCodes`: Position Schedule Codes
- `positionOfferingCode`: Position Offering Code
- `publicationDate`: Publication Date

All 7 declared fields: `references/output-fields.json`.

## Inputs

| Field | Type | Required | Default | Notes |
|---|---|---|---|---|
| `mode` | string | yes | search | What to fetch. |
| `searchQuery` | string | no | developer | Free-text keyword to search for (mode=search). Matches job title, description and employer name depending on `searchIn`. |
| `searchIn` | string | no | EVERYWHERE | Where the search query is matched. |
| `jobIds` | array | no | [] | EURES job vacancy IDs or full detail-page URLs, as found in the `jobId` or `sourceUrl` output field, e.g. |
| `countries` | array | no | [] | Restrict results to job locations in these countries. Leave empty for all EEA countries. |
| `regionCodes` | array | no | [] | Restrict results to job locations in these region codes (finer-grained than `countries`), e.g. `deb` for Berlin (Germany) or `no0b` for Trondelag (Norway). |
| `sectors` | array | no | [] | Restrict results to these NACE Rev.2 business sectors. |
| `positionOfferingCodes` | array | no | [] | Restrict results to these contract/position offering types. |
| `positionScheduleCodes` | array | no | [] | Restrict results to these work schedules. |
| `educationLevels` | array | no | [] | Restrict results to these required education levels. |
| `experienceLevels` | array | no | [] | Restrict results to these required-experience bands. |
| `languageSkills` | array | no | [] | Restrict results to jobs requiring at least basic proficiency in these languages. |
| `occupationUris` | array | no | [] | Restrict results to jobs classified under these ESCO occupation URIs or broader ISCO group URIs. |
| `skillUris` | array | no | [] | Restrict results to jobs requiring these ESCO skill URIs. Copy values from the `requiredSkills` field of a previous `mode=byIds` result, e.g. |

7 more optional fields on the Actor's Input tab.

Example (`references/example-input.json`):

```json
{
  "maxItems": 25,
  "mode": "search"
}
```

The input passes the Actor's input schema (checked at every publish). First run: `maxItems` = 25, small enough for the 300-second sync wait; raise it once the rows look right.

## Run it

Set `APIFY_TOKEN`, then call the synchronous endpoint for small and medium runs (it waits up to 300 seconds):

```bash
curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~eures-cross-border-job-search-and-vacancy-lookup/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @references/example-input.json > output.json
```

Or with Node 18+: `node scripts/run.mjs [input.json]`.

For large runs, start an async run and read its dataset when it finishes:

```bash
RUN=$(curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~eures-cross-border-job-search-and-vacancy-lookup/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
  -d @references/example-input.json)
RUN_ID=$(echo "$RUN" | jq -r '.data.id'); DATASET=$(echo "$RUN" | jq -r '.data.defaultDatasetId')
curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?waitForFinish=60" -H "Authorization: Bearer $APIFY_TOKEN" | jq -r '.data.status'
curl -s "https://api.apify.com/v2/datasets/$DATASET/items?format=json" -H "Authorization: Bearer $APIFY_TOKEN" > output.json
```

## Cost and limits

- Apify bills the Actor's usage on your account; the Actor's Pricing tab shows the current price.
- Keep the limit in the input small for a first run.

## Guardrails

- Public data only. Do not pass cookies, sessions or private account data.
- Do not use the output for spam, harassment or unlawful discrimination.
- Check the target site's terms and local law before running at scale.