Iraq Jobs Foundation Scraper
Pricing
from $5.00 / 1,000 results
Iraq Jobs Foundation Scraper
Collect public Iraq job listing metadata from the Iraq Jobs Foundation website, including titles, cities, categories, job types, salaries, and dates.
Pricing
from $5.00 / 1,000 results
Rating
0.0
(0)
Developer
LIAICHI MUSTAPHA
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
23 days ago
Last modified
Categories
Features
Share
Collect public job-listing metadata from Iraq Jobs Foundation using its unauthenticated jobs endpoint.
Features
- Paginates the public listing endpoint and deduplicates records by source ID.
- Captures titles, employer labels, location, category, job type, salary and source dates/status.
- Uses a single request at a time with a one-second minimum gap.
- Limits collection with
maxItemsandmaxPages. - Excludes full descriptions and application methods because those fields may contain personal contact information.
- Saves run counts and source pagination metadata to the
STATSkey-value record.
Use cases
- Explore the job-posting mix visible on this platform.
- Compare locations, categories, job types, and the presence of salary/deadline data.
- Build a timestamped snapshot for market research.
The dataset represents source listing records, not necessarily individual positions: one post may advertise several roles. It is not a census of Iraq's labor market, and the source's isActive flag is not independent verification that a vacancy remains open.
Input
| Field | Type | Default | Description |
|---|---|---|---|
maxItems | integer | 5000 | Maximum unique records to save (1–10,000). |
maxPages | integer | 100 | Maximum listing pages to request (1–100). |
The API currently returns up to 100 records per page. A run with maxItems: 5000 and maxPages: 100 collects the full inventory when the source has fewer than 5,000 records.
Output
Records include job_id, title, company, location, category, job_type, salary, deadline, is_active, approval_status, views, created_at, updated_at, source/API URLs, and scraped_at.
Example:
{"job_id": "2749","title": "Kurdistan Save the Children is looking for qualified candidates to join its teams across Slemani, Darbandikhan, and Kirkuk","company": "Not specified","location": "Sulaymaniyah","category": "Finance","job_type": "full-time","salary": null,"deadline": null,"is_active": true,"approval_status": "approved","views": 13,"created_at": "2026-10-09T06:54:16.000Z","updated_at": "2026-10-09T11:45:18.000Z","source": "Iraq Jobs Foundation","country": "Iraq","source_url": "https://www.ijobsiq.com/jobs","source_api_url": "https://www.ijobsiq.com/api/jobs?page=1&limit=100","scraped_at": "2026-10-09T11:50:37.665Z"}
Notes
- Counts and fields can change between runs. Preserve
scraped_atwhen analyzing snapshots. - The collector uses the publicly accessible listing endpoint and does not fetch full job descriptions, application links, or contact details.
- Before public distribution or commercial use, confirm that collection and downstream use comply with the source's current terms and applicable rules.
FAQ
Does a record equal one vacancy? Not always. A single post may list multiple roles, and duplicate/reposted content may exist under separate IDs.
Does is_active: true prove the job is still open? No. It reports the source's current flag only; deadlines may be missing or outdated.
Why are descriptions and application details absent? They can contain direct contact information. This actor is designed for aggregate analysis, not collecting applicant contact targets.