Bumeran Jobs Scraper — 7 LATAM Countries | PPE

Bumeran Jobs Scraper for LATAM Jobs

Extract public job listings from Bumeran and sibling Navent boards across seven LATAM countries, with structured company, location, dates, modality, and description data. Run it from your Apify account without a buyer API key, cookie, or source login.

• Search each query independently across selected brands and countries.
• Compare companies, locations, work types, and modalities by role and city.
• Monitor publication and modification timestamps; compare contentHash values between your own runs to spot changes.
• Add full descriptions plus area, seniority, contract type, benefits, and required skills with fetchDetails.
• Download records for a job board, recruiting CRM, or hiring-company lead list.

What you get

Field family	Fields	Type	Availability and notes
Identity	id, url, title, company, brand, source	String	Identifier, URL, employer, brand, and source site
Location	city, province, countryName	String	Parsed listing location
Employment	workType, workModality, vacancies, isQuickApply, listingType	String, integer, boolean	Arrangement, vacancy count, application flag, and plan
Dates	publishDate, publishDateISO, lastModifiedISO, expiryDate, scrapedAt	String	Publication, modification, and collection timestamps; expiryDate is filled only with fetchDetails = true
Descriptions	descriptionHtml, descriptionText, descriptionMarkdown	String	Always present. With fetchDetails = false all three hold the same listing excerpt from search; with true they hold the full HTML plus converted text and Markdown
Classification	area, subArea, seniority, contractType	String	Filled only with fetchDetails = true; empty strings otherwise
Lists	benefits, requiredSkills	Array	Filled only with fetchDetails = true; empty arrays otherwise or when the listing has none
Flags and tracking	isConfidential, isAccessible, isRepost, changeStatus, contentHash	Boolean, string	isRepost is always false and changeStatus is always "NEW"; only contentHash is derived (from job ID, title, company, and description text). To detect changes, compare contentHash between runs yourself

Sample output

This record came from a run with fetchDetails = false, so benefits and requiredSkills are empty and area, seniority, contractType, and expiryDate are blank (omitted here). In this record city and province were empty (other listings fill them, for example "Capital Federal" and "Buenos Aires"). Fields not shown are omitted, and descriptionHtml is cut for length; other values are copied from the real record.

{
  "id": "1118494651",
  "url": "https://www.bumeran.com.ar/empleos/job-1118494651.html",
  "title": "NodeJs Developer",
  "company": "ITSM CONSULTING SA",
  "brand": "www.bumeran.com.ar",
  "countryName": "Argentina",
  "workType": "Full-time",
  "workModality": "Remoto",
  "publishDate": "23-10-2026",
  "publishDateISO": "2026-10-23T16:25:16Z",
  "lastModifiedISO": "2026-10-23T16:25:16Z",
  "descriptionHtml": "Empresa líder Partner de Microsoft con mas de 20 años impulsando la tecnología de punta en Latinoamérica. […]",
  "benefits": [],
  "requiredSkills": [],
  "changeStatus": "NEW",
  "contentHash": "e18f1dbb6134adbd",
  "scrapedAt": "2026-10-29T05:38:44Z"
}

Pricing

This Actor uses pay-per-event pricing.

• apify-actor-start: $0.00005 per event on the Free plan. It is charged when the Actor starts; the number of events depends on Actor memory, with a minimum of one event.
• apify-default-dataset-item: $0.001 per event on the Free plan. One event represents one scraped result with all fields. On the Free plan, 1,000 events cost $1 and 10,000 events cost $10.
• The job-listing event has no price, so the buyer is not charged for it.

With 100 results and the minimum one Actor Start event, 100 results = $0.10005 on Free. A single Free-plan run returns at most 10 items (see Limits), so 100 results take several runs or a paid plan.

The Apify Free plan's $5 monthly credit covers about 4,999 results at these prices.

Actor charges are separate from platform usage: compute, Apify Proxy traffic including residential traffic, and storage are included in the event prices and paid by the Actor developer. This Actor does not pass those platform-usage charges to the user.

How to use

1. Open the Actor page in Apify.
2. Enter one or more searchQueries; each runs independently for each selected brand.
3. Choose valid brand keys for the countries and boards to search.
4. Set fetchDetails to true for detail-response fields such as benefits, seniority, contract type, and required skills.
5. Set result and page limits, choose fechaOnline DESC for newest-first ordering, and keep the Apify RESIDENTIAL proxy configuration.
6. Run the Actor, wait for the dataset, and download the records.
7. Repeat the run through Apify Schedules, using daily as a starting point for job listings.

{
  "brands": ["bumeran-ar", "laborum-cl"],
  "searchQueries": ["developer"],
  "fetchDetails": true,
  "maxItems": 20,
  "maxPagesPerQuery": 1,
  "sort": "fechaOnline DESC",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

This recipe needs a paid plan: a Free-plan run keeps only the first brand and the first query and returns at most 10 items, so the two brands and 20 items above are not reachable on Free in one run.

Export the dataset as JSON or CSV, or read it through the Apify dataset API.

Input parameters

Parameter	What it does	Default
brands	Array of allowed keys: bumeran-ar (Argentina), zonajobs-ar (Argentina), laborum-cl (Chile), multitrabajos-ec (Ecuador), bumeran-mx (Mexico), konzerta-pa (Panama), bumeran-pe (Peru), and bumeran-ve (Venezuela).	["bumeran-ar"]
searchQueries	Required array of job keywords; each query runs independently for each brand. If omitted at runtime, the Actor uses ["developer"].	Required in the input schema
fetchDetails	Makes one extra request per listing and adds the full HTML description, area, seniority, contract type, benefits, and required skills.	false
maxItems	Maximum total listings across brands and queries. Accepted range: 1–5000.	100
maxPagesPerQuery	Maximum pages per query; each page returns up to 20 listings. Accepted range: 1–100.	5
sort	API sort expression: fechaOnline DESC for newest first or an empty string for relevance.	"fechaOnline DESC"
proxyConfiguration	Apify proxy configuration; an Apify RESIDENTIAL proxy is required for reliable access.	Apify RESIDENTIAL proxy configuration

Limits and edge cases

Condition	What you see	What to do
The run uses the Free plan	One brand and one query are kept; the run is limited to 10 items and one page per query.	Use a paid plan for configured multi-brand, multi-query, or higher-volume scope.
maxItems or maxPagesPerQuery reaches its limit	Collection stops at the total item or page limit; maxItems applies across brands and queries.	Increase the setting within its accepted range.
A page returns no listings	Pagination for that query stops, so fewer items may be returned.	Check searchQueries, then try another query or brand.
A brand key is not recognized	The unknown brand is skipped.	Use a supported key listed under Input parameters.
A search request returns HTTP 403, 406, or 429, or another search request fails	Pagination for the affected brand and query stops; pushed records remain in the dataset.	Keep the Apify RESIDENTIAL proxy configuration and rerun if needed.
A detail request fails with fetchDetails enabled	The listing is normalized, but detail-response fields can remain empty.	Review base fields or rerun with details enabled.

FAQ

How much does it cost to scrape Bumeran and the sibling Navent job boards?

Each dataset result is one apify-default-dataset-item event; see Pricing for the totals.

Why did my run return no or fewer listings?

A query or page can be empty, or the run can reach a limit listed under Limits and edge cases. Try another query or supported brand.

What should I do if a run is not working?

Confirm that proxyConfiguration uses the Apify RESIDENTIAL proxy. Search requests returning HTTP 403, 406, or 429 stop pagination for the affected brand and query, so review the run and retry with the recommended proxy and narrower scope.

Why are some detail fields empty?

area, seniority, contractType, benefits, and requiredSkills come from an additional detail request. Set fetchDetails to true; if that request fails, those fields can remain empty.

Is it legal or allowed to scrape this public job data?

The Actor collects public search data from Bumeran and sibling Navent job boards. Whether a particular use is legal or allowed depends on applicable law, the source's terms, and your use case; review those requirements before using the data.