Jobberman Scraper
Pricing
from $0.87 / 1,000 job listings
Jobberman Scraper
Extract job listings from Jobberman.com, Nigeria's largest job board. Get title, company, salary, location, job function and posting date for any search query. Structured JSON output, pay per result.
Pricing
from $0.87 / 1,000 job listings
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Jobberman Nigeria Job Scraper — Salary, Description, Company
Search Jobberman.com — Nigeria's largest job board — by keyword or direct URL and get back structured job listings: title, company, location, salary range, employment type, experience level, and the full job description in HTML, plain text, and Markdown.
What it does
The actor runs a two-step crawl. First it fetches Jobberman's search-results pages for your keyword(s) and collects the listing URLs from each result card. Then it opens every listing's detail page, where the real data lives: each page carries a single application/ld+json block (schema.org JobPosting) plus a window.dataLayer object with the human-readable company name, location, and work-type text. The actor reads both sources and merges them into one clean record per job — no browser rendering needed, the site serves the data server-side.
Input
- Queries — one or more search keywords (e.g.
"manager","accountant"). Each keyword paginates through Jobberman's search results (16 listings per page) until a page returns no results ormaxItemsis reached. - Start URLs — optional direct
jobberman.com/jobs?...search-result URLs (with your own site filters applied) or directjobberman.com/listings/...job URLs, for when you already know exactly what to scrape. - Max items — maximum number of job listings to return (default 100, up to 5000).
- Proxy configuration — Apify Proxy, RESIDENTIAL group, prefilled and ready to use out of the box.
Output fields
Each result is one job listing with:
jobId,url,title,company,location,countryindustry,occupationalCategory,employmentType,qualifications,experienceMonthsdescriptionHtml,descriptionText,descriptionMarkdown— the same job description in three formatsdatePosted,applicationDeadline,directApplysalaryMin,salaryMax,salaryCurrency,salaryPeriod— present when the employer publishes a salary; Jobberman marks many listings "Confidential," in which case these fields come back empty rather than guessedscrapedAt
Pricing
Pay-per-result — see the Store pricing tab for the current per-listing price. You're only charged for listings that are successfully scraped and returned; a failed detail fetch (e.g. a listing that 404s) is skipped and not charged.
Notes
Jobberman doesn't expose a total-result count on its search pages, so the actor paginates until a page comes back empty or your maxItems cap is hit. Salary data is genuinely only present on listings where the employer chose to disclose it — that's a source data-sparsity fact, not a parsing gap. Company officer/registry-style data is not part of Jobberman's listing pages and isn't returned here.
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.