Kariyer.net Scraper — Turkey Job Listings

Kariyer.net Job Listings Scraper

Extract structured job listings from Kariyer.net, Turkey's largest job board, by keyword and page. This actor is built for recruiters, staffing agencies, market researchers and job-board aggregators who need fresh, structured Turkish job-market data without maintaining their own scraper. It reads Kariyer.net's server-rendered search-result cards — no login, no CAPTCHA-solving required on your end.

Features

• Search Kariyer.net by any keyword or phrase (job title, skill, company)
• Paginate across multiple result pages in a single run
• Returns up to 40 structured fields per listing: title, company, location, sector, employment type, work model, sponsorship flag, publish/closing dates, company/sector/city/country IDs, job code, and more
• Deduplication signal (contentHash, isRepost) so you can filter re-posted listings
• Built-in Turkish residential proxy by default — works out of the box, zero manual proxy setup
• Pay-per-result pricing — you only pay for listings actually delivered

How to use

1. Click Start, or open the actor's page and hit Try for free.
2. Enter a searchQuery (e.g. "yazilim", "muhasebe", "satis") — defaults to "developer".
3. Set maxResults and pagesToFetch if you need more than the default sample.
4. Run. Results stream into the dataset as they're scraped — no waiting for the full run to finish before you can start exporting.
5. Export the dataset as JSON/CSV/Excel, or pull it via the Apify API into your own pipeline.

Input & Output example

Input:

{
  "searchQuery": "yazilim",
  "maxResults": 20,
  "pagesToFetch": 1
}

Output (one record):

{
  "id": "4502622",
  "title": "Çağrı Merkezi Müşteri Temsilcisi",
  "company": "N2mobil Takip Sistemleri A.Ş",
  "location": "Ankara",
  "workModel": "İş Yerinde",
  "employmentType": "Tam zamanlı",
  "isSponsored": true,
  "publishDateISO": "2026-07-17",
  "url": "https://www.kariyer.net/is-ilani/...",
  "source": "kariyer.net"
}

Each delivered job can contain the following fields: id, url, title, company, companyWebsite, location, district, workModel, employmentType, positionLevel, experienceLevel, departmentName, applicationCount, sectorName, companySize, companyIndustry, countryName, isSponsored, jobDateStatus, publishDate, publishDateISO, closingDate, salaryMin, salaryMax, salaryCurrency, salaryPeriod, benefits, descriptionHtml, descriptionText, descriptionMarkdown, contentHash, isRepost, originalPublishDate, originalUrl, source, scrapedAt, companyId, sectorId, cityId, countryId, jobCode. Fields unavailable from the listing pages are returned as null — the actor does not perform detail-page enrichment, so description/salary/benefit fields are populated only when Kariyer.net exposes them directly on the listing card.

Pricing

This actor uses pay-per-event (PPE) billing. One job-listing event is charged per delivered job at USD 0.0018. Scraping 1,000 job listings costs approximately $1.80. There is also a negligible Actor-Start event (~$0.00005) charged once per run. You only pay for what's actually delivered — a run that returns 0 results costs nothing beyond the start fee.

FAQ / Disclaimers

• Does this need my own proxy? No — a Turkish residential proxy is wired in by default; you can override it via the proxyConfiguration input if you have your own Apify Proxy setup.
• Does it log in to Kariyer.net? No — it reads only publicly available search-result pages.
• Detail-page fields (full description, salary) are missing — why? This actor intentionally scrapes only the search-result listing cards for speed and cost efficiency; fields that only exist on the individual job-detail page come back as null.
• Found a bug or need a custom variant (detail-page enrichment, other countries)? Open an issue on the actor's Issues tab.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.