← data exports  /  apify actor

Rozee.pk Jobs Scraper

how to get the data with our Apify actor rozeepk-jobs-scraper

Scrape job listings from Rozee.pk by keyword and optional city. Returns job title, company, location, type, experience required, skills, description, posted date, and application deadline.

on apify
v0iddo/rozeepk-jobs-scraper
category
jobs, automation
build
0.1.3, built 2026-11-18
billing
Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

  • Job ID (jobId)
  • title
  • company
  • city
  • Job Type (jobType)
  • experience
  • Salary Min (salaryMin)
  • Salary Max (salaryMax)
  • currency
  • skills
  • Posted Date (postedDate)
  • Apply By (applyBy)
  • Job URL (url)

What people use it for

  • Pakistan job search: openings by keyword and city, with company, job type, experience required and apply deadline.
  • Skill demand research: see which skills employers list for a role such as developer or accountant.
  • Salary data: PKR salary minimum and maximum for the listings that show them, which are a minority.
  • Recruitment agencies: track which companies hire in Karachi, Lahore or Islamabad and when jobs were posted.

Run it on Apify

  1. Open rozeepk-jobs-scraper on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

  • Search Keywords (keywords): One or more job search keywords, e.g. developer, accountant, manager. Each keyword is fetched as a separate search.
  • City Slug (city): Optional city slug to filter results, e.g. karachi, lahore, islamabad, rawalpindi. Leave blank to search all cities in Pakistan.
  • Pages per Keyword (maxPages): How many result pages (up to 20 jobs each) to read per keyword. Default: 3.
  • Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
  • Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson
{
  "keywords": [
    "developer"
  ],
  "city": "",
  "maxPages": 1,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "keywords": ["developer"],
    "city": "",
    "maxPages": 1,
    "maxItems": 20,
}
run = client.actor("v0iddo/rozeepk-jobs-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • Each result page returns up to 20 jobs; set maxPages to control how many pages are read per keyword.
  • The city slug must match the Rozee.pk URL format (e.g. karachi, lahore, islamabad). Leave it blank to search all of Pakistan.
  • Salary figures (salaryMin, salaryMax in PKR) are included in the output when the listing discloses them; most listings on Rozee.pk do not show salary publicly.
  • Not affiliated with Rozee.pk.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on Rozeepk, cookies or an API key?

No. The actor reads only what every visitor of Rozeepk can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

every fact here is read from the actor's public data on Apify, every day; it last changed on