Eleman.net Turkey Jobs Scraper | İş İlanları

Eleman.net Turkey Jobs Scraper

Extract Turkish job listings from Eleman.net, including title, company, location, summary, phone-application status, logo, and listing link. No API key or login is needed; search by keyword or collect newest listings.

• Get one dataset row per listing with duplicates removed.
• Scrape keyword results or the newest-listings mode across multiple pages.
• Build job aggregation feeds from listing titles, summaries, and links.
• Research hiring by company, role, city, and district from one dataset.

What you get

The Actor reads public Eleman.net search pages and returns one normalized dataset row per job listing. Duplicate listings are removed.

Field	Description
jobId	Eleman.net listing ID taken from the listing link
title	Job title
company	Company name
location	City or district text shown on the listing
summary	Short listing summary or teaser
phoneApplication	true when the listing offers application by phone
logoUrl	Company logo URL, or null when unavailable
jobUrl	Link to the listing on Eleman.net
query	Search term that found the listing; null in newest-listings mode
scrapedAt	UTC timestamp in ISO 8601 format
parse_confidence	Share of the core fields title, company, and jobUrl that were found, from 0 to 1

Sample output

This is one real record from the dataset sample; the second sample record is omitted.

{
  "jobId": "4797016",
  "title": "Ticari Ve Sektörel Yazılımlar Destek Personeli",
  "company": "Selvi Bilgisayar - İsmail Selvi",
  "location": "Antalya",
  "summary": "Yemek",
  "phoneApplication": false,
  "logoUrl": null,
  "jobUrl": "https://www.eleman.net/is-ilani/ticari-ve-sektorel-yazilimlar-destek-personeli-i4797016",
  "query": "yazilim",
  "scrapedAt": "2026-10-30T01:37:46Z",
  "parse_confidence": 1
}

Pricing

The billing model is pay per event. A job-result event is one returned job listing with all fields.

An apify-actor-start event is charged when the Actor starts: one event per GB of Actor memory, minimum one event.

Plan	apify-actor-start per event	job-result per event
Free	$0.00005	$0.00265
Bronze	$0.0000495	$0.0026235
Silver	$0.000049	$0.002597
Gold	$0.0000485	$0.0025705
Platinum	$0.000048	$0.002544
Diamond	$0.0000475	$0.0025175

Worked example: 1,000 x $0.00265 = $2.65 on the Free plan for job-result events, plus one start event at $0.00005.

For 10,000 results: 10,000 x $0.00265 = $26.50 on the Free plan.

The Apify Free plan includes $5 of monthly platform usage credit. At Free-plan prices, that covers about 1,886 job-result events after the start charge. Free-plan runs return a preview of up to 25 results; paid plans have no preview limit.

For this pay-per-event Actor, compute, Apify Proxy traffic including residential traffic, and storage are included in the event prices and paid by the Actor developer. Platform usage is not billed to you separately.

How to use

1. Enter one or more Turkish keywords in searchTerms, such as yazilim, garson, or muhasebe. Use an empty array to collect the newest listings instead.
2. Set pagesToFetch for the number of listing pages to fetch per term. Each page contains 30 listings, and the accepted range is 1 to 100.
3. Limit the output with maxItems. The limit applies across all terms and pages; use 0 for no cap.
4. Keep the default proxy settings (residential, country TR). They are already set up; you do not need your own proxy or any login.
5. Start the run, then open the Job listings table or export the dataset.
6. Repeat the run through Apify Schedules, using daily as a starting point for job listings.

Export the dataset as JSON or CSV.

Use this input to search for yazilim across three pages:

{
  "searchTerms": ["yazilim"],
  "pagesToFetch": 3,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "TR"
  }
}

Input parameters

Parameter	What it does	Default
searchTerms (array of strings)	Keywords to search on Eleman.net. An empty array selects newest-listings mode.	Prefill: ["yazilim"]
pagesToFetch (integer)	Number of listing pages to fetch per search term. Each page contains 30 listings. Accepted range: 1 to 100.	3
maxItems (integer)	Maximum number of listings returned across all terms and pages. 0 means no cap. Any value of 0 or higher is accepted.	100
proxyConfiguration (object)	Proxy settings used to reach Eleman.net. The default is residential traffic with country TR.	Residential, country TR
disableUsageStats (boolean)	Turns off the usage-statistics records described below when set to true.	false

Limits and edge cases

Condition	What you see	What to do
pagesToFetch is outside the accepted range	The input does not match the schema range of 1 to 100 pages per term.	Use a value from 1 through 100.
maxItems is 0	There is no cap, although the Free-plan preview limit still applies.	Set a positive value when you want an explicit output cap.
The Free plan is used	The run returns a preview of up to 25 results.	Use a paid Apify plan for runs without the preview limit.
A search page contains no parsed listings	A page that loads normally but has no parsed listings ends fetching for that term at once, with no retry.	Check the keyword, try newest-listings mode with an empty searchTerms array, or run again.
A page has a transport error or is detected as blocked (HTTP 401, 403, 429 or 503, a very small page, or a page without listing markers)	The Actor retries the page up to three attempts. If it still cannot fetch the page, it gives up on that page and that term; rows already pushed from earlier pages remain in the dataset, and processing can continue with the next search term.	Run again and keep the default proxy settings.
Listings overlap across pages or search terms	Duplicate listings are removed, so the row count can be lower than the total page capacity.	Use the returned dataset as the deduplicated result set.
A listing does not expose a logo or another parsed value	The corresponding output field can be null, and parse_confidence reflects whether the core fields were found.	Use the available fields and inspect parse_confidence when filtering results.
A row has neither a listing URL nor a title	The row is skipped rather than added to the dataset.	Review the run logs and retry if the result is unexpectedly incomplete.

FAQ

How much does it cost to scrape Eleman.net Turkey job listings?

On the Free plan, 1,000 x $0.00265 = $2.65 for 1,000 job-result events, plus the start charge. Prices for the Bronze to Diamond plans are in the Pricing table above.

Why did my run return no listings?

An empty result can occur when the first search page contains no parsed listings, or when that page cannot be fetched after 3 attempts. Try a Turkish keyword that matches the role, use an empty searchTerms array for newest-listings mode, or run the Actor again with the default proxy settings.

Do I need an API key, login, or my own proxy?

No. You need no API key and no Eleman.net login. The residential Turkey proxy is already configured, so you do not need your own proxy.

Why did the run end before all pages were fetched?

The Actor stops a term at the first page with no parsed listings, or after 3 failed attempts on a page (transport error or detected block). Rows already saved stay in the dataset; later pages for that term may be missing.

Is using Eleman.net public data legal or allowed?

This Actor collects public job-search pages from Eleman.net without requiring a login. Whether a particular use is legal or allowed depends on the source terms and applicable law for your use case; review those requirements before using the data.

Related actors

• FreeJobAlert India Govt Jobs Scraper | Sarkari Naukri — related job-listing scraper for India government jobs.
• Saramin Korea Jobs Scraper | 사람인 채용정보 — related job-listing scraper for Korea.
• Worknet Korea Jobs Scraper | 고용24 Job Postings — related Korean job-postings scraper.

Usage statistics

This Actor creates a small, content-free summary at the end of each run, used only to monitor reliability and improve this Actor. No input values, credentials or scraped data are sent.

A copy of the exact record for your run is saved as USAGE_STATS in your own Apify key-value store.

To opt out, set disableUsageStats to true in the input. Nothing is sent then.

Full list of collected fields