Bumeran Jobs Scraper — Latin American job board avatar

Bumeran Jobs Scraper — Latin American job board

Pricing

from $1.20 / 1,000 job rows

Go to Apify Store
Bumeran Jobs Scraper — Latin American job board

Bumeran Jobs Scraper — Latin American job board

Scrape Bumeran (Argentina, Peru, Mexico, Venezuela) and Laborum Chile job ads: title, company, city, province, work modality, posting age, area, ad ID and URL.

Pricing

from $1.20 / 1,000 job rows

Rating

0.0

(0)

Developer

Mike Major

Mike Major

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

15 days ago

Last modified

Categories

Security

Limited permissions

Share

Bumeran Jobs Scraper

Collects job ads from Bumeran — the Jobint board for Argentina, Peru, Mexico and Venezuela — and from its Chilean sibling Laborum. One record schema across five country sites.

~$1.20 per 1,000 jobs ($0.0012 per row). 100 results per request, no login, no account. The actor runs on the site's own JSON search endpoint, so a run is seconds, not minutes.

What you get

One row per ad: id, title, company (or Confidencial), city, province, work modality (Presencial / Híbrido / Remoto), posting-age text, exact posting timestamp, employment type, area, canonical URL and the country searched.

Input

FieldDefaultNotes
countryarar, pe, mx, ve, cl (cl = laborum.cl)
queryemptyJob title or field: vendedor, ingeniero, cajero. Empty = the country's whole feed
maxItems200Hard cap, 10,000 maximum per run
orderByrecentor relevance
proxyConfigurationdirectOnly needed if the board rate-limits your IP; Apify proxy works

Output sample

Real rows from a cloud run ({"country":"ar","maxItems":5,"query":"vendedor"}, run 6alY2KiOTgIr9fitu):

{
"adId": "1118383737",
"title": "Vendedor",
"company": "ICASE",
"city": "Avellaneda",
"province": "Buenos Aires",
"modality": "Presencial",
"postedText": "Nuevo",
"postedAt": "2026-10-22T10:19:44.000Z",
"employmentType": "Full-time",
"category": "Comercial, Ventas y Negocios",
"url": "https://www.bumeran.com.ar/empleos/vendedor-icase-1118383737.html",
"originalUrl": "https://www.bumeran.com.ar/empleos/vendedor-icase-1118383737.html",
"searchCountry": "ar",
"scrapedAt": "2026-10-23T00:09:44.669Z"
}
{
"adId": "1118489849",
"title": "Vendedor/a",
"company": "Confidencial",
"city": "Capital Federal",
"province": "Buenos Aires",
"modality": "Presencial",
"postedText": "Publicado hace 1 día",
"postedAt": "2026-10-21T11:39:13.000Z",
"employmentType": "Full-time",
"category": "Comercial, Ventas y Negocios",
"url": "https://www.bumeran.com.ar/empleos/vendedor-a-confidencial-1118489849.html",
"originalUrl": "https://www.bumeran.com.ar/empleos/vendedor-a-confidencial-1118489849.html",
"searchCountry": "ar"
}

Coverage and limits

  • The site caps any search at 1,200 ads (12 requests of 100). A single query cannot go deeper; split by query and dedupe on adId for larger pulls.
  • orderBy maps to the site's RECIENTES / RELEVANTES sort parameter. The portal currently returns near-identical ordering for both, so treat relevance as a hint, not a guarantee.
  • No salary field: the board only exposes a "salary required" flag, not an amount. Nothing invented here.
  • postedText is Nuevo for ads under 24 h and Publicado hace N días beyond that, derived from the absolute postedAt the site returns.
  • url is rebuilt from title + company + id. Where the company is confidential (or the posting name changed) the site answers 301 to the canonical slug — follow the redirect.
  • Ads are deduplicated by adId inside a run; the same vacancy is never emitted twice.
  • Modality and city come from the ad's own location block, so they are as accurate as the employer made them.

Example

{ "country": "cl", "query": "cajero", "maxItems": 500, "orderBy": "recent" }

Pricing

Pay per event: $0.0012 per job row, plus a $0.0001 actor start. Platform usage is included, so a 1,000-job run bills about $1.20 and nothing else.

Notes on use

Job ads are public pages. The actor requests the public /empleos.html listing (server-rendered HTML with a crawler user agent) and always hits the JSON search endpoint first, falling back to the HTML listing if that endpoint ever changes shape. Cite Bumeran or Laborum as the source when republishing in bulk.