eJobs.ro Scraper — Romania Job Ads & Company Leads

Export job ads from eJobs.ro, Romania's largest job board — hiring company, cities and counties, industry, department and dates — to JSON, CSV or Excel. Keyless, no login.

What does eJobs.ro Scraper do?

eJobs.ro answers a public JSON API with no key, no account and no cookie. Roughly 15 000 ads are live at any time.

Two details decide how this Actor is built. First, the list endpoint stops returning rows past about page 20, so a single query can never reach the whole board — the Actor sweeps the site by replaying every department and industry name as a search term and de-duplicating on job ID. Second, list rows carry taxonomy IDs, not names: city 16, industry 8. The Actor loads the city, county, industry, department and language reference tables once and resolves them locally, so every row ships readable values instead of raw integers.

Each row identifies the hiring company with its verified badge and its total number of open positions — the signal that separates a one-off vacancy from an employer worth prospecting.

Who is it for?

• Recruitment agencies mapping which Romanian companies are hiring and in which county.
• B2B sales teams using hiring volume as a growth signal for account targeting.
• Job boards and aggregators that need a Romanian feed without a data licence.
• Market analysts tracking demand by industry, department and city.
• HR-tech vendors prospecting employers who publish roles continuously.

Use cases

• Build a list of every verified company hiring in IT across Bucharest and Cluj.
• Rank employers by open-position count to find the fastest-growing accounts.
• Track how many logistics roles appear per county, month over month.
• Feed a niche Romanian job board with fresh listings and direct ad links.
• Spot the moment a target company posts its first sales role.

Why use this Actor?

• Keyless — no account, no token, no login.
• 28 structured fields, with taxonomy IDs already resolved to names.
• Sweeps past the paging ceiling by replaying department and industry terms.
• Company signal included — verified employer flag, plus total open positions when detail fetch is on.
• Coordinates included where eJobs publishes them, ready for mapping.
• Optional requirements text — one extra request per ad, off by default.

What data can you extract?

Field	Type	Description
jobId	string	eJobs ad ID
title	string	Job title
slug	string	URL slug
jobUrl	string	Public ad page
companyName	string	Hiring company
companyId	string	Company ID
companySlug	string	Company page slug
companyVerified	boolean	eJobs verified employer
companyLogoUrl	string	Company logo
companyOpenPositions	number	Total openings at the company (detail fetch only)
positions	number	Positions in this ad
cities	string	City names, comma-separated
counties	string	County names (detail fetch only)
industries	string	Industry names
departments	string	Department names
languages	string	Required languages
latitude / longitude	number	Coordinates where published
jobType	string	Ad status, e.g. active
creationDate	string	First published
expirationDate	string	Expiry
republishDate	string	Last republished
lastModified	string	Last edit
requirements	string	Requirements text (only when detail fetch is on)
presentationImageUrl	string	Employer presentation image
country	string	Romania
source	string	Always ejobs_ro
scrapedAt	string	Run timestamp (ISO 8601)

Example output

{
  "jobId": "1977725",
  "title": "Team Leader (f/m/d)",
  "jobUrl": "https://www.ejobs.ro/user/locuri-de-munca/team-leader-f-m-d/1977725",
  "companyName": "MODIVO ROMANIA S.A.",
  "companyVerified": true,
  "positions": 8,
  "cities": "București, Craiova, Brăila",
  "industries": "Retail / Comerț",
  "creationDate": "2026-08-07T19:13:11Z",
  "expirationDate": "2026-09-06T00:00:00Z",
  "jobType": "active",
  "source": "ejobs_ro"
}

How to use it

1. Enter a keyword, or leave it empty to sweep the whole board.
2. Turn on Fetch requirements text only if you need the requirements block — it costs one extra request per ad.
3. Set Maximum results.
4. Run, then export JSON, CSV or Excel.

Input example

{
  "query": "",
  "maxResults": 5000
}

Notes and limits

• eJobs honours only free-text search as a filter; city and industry filters are not exposed by the API. The Actor works around this by sweeping taxonomy terms, so a full-board run returns overlapping searches that are de-duplicated by job ID.
• A single search stops at roughly 2 000 rows. Deeper coverage comes from the sweep, not from paging.
• The API does not publish salary. Ads that mention pay do so inside the requirements text.
• requirements, counties and companyOpenPositions live on the ad detail, not the list feed. Switch on Fetch requirements text to populate them; with the option off they stay null by design rather than pretending to be data.
• You are responsible for how you use employer data, including under GDPR.

FAQ

Do I need an eJobs account? No. The API is public and this Actor needs nothing from you.

Why are city and industry filters missing from the input? Because eJobs ignores them on the API. Filter the exported dataset instead — every row carries resolved city, county, industry and department names.

Can I get more than 2 000 ads? Yes. Leave the keyword empty and the Actor sweeps department and industry terms to go deeper.

Is salary included? No. eJobs does not expose a salary field; when pay is mentioned it sits inside the requirements text.

How am I charged? Pay per result — you pay for the ads delivered.