Computrabajo Scraper: LATAM Jobs and Salaries
Scrape job postings from Computrabajo in 18 Latin American countries: title, company with rating, city, region, salary with currency and period, contract, schedule, remote or hybrid, education, experience, skills, industry and dates. Search by keyword and city or paste URLs.
- on apify
v0iddo/computrabajo-scraper- category
- jobs, automation
- build
- 0.1.12, built 2026-11-03
- 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:
titlecompanycitycountry- Salary (
salaryText) - Contract (
contractType) schedule- Work mode (
workMode) - Posted (
postedDate) - Posting (
url)
What people use it for
- Latin American salary benchmarks: collect the monthly pay of a job title by country and city, in local currency.
- Recruitment agencies and HR: see which employers hire, how often they post and which roles stay confidential.
- Job boards and newsletters: a daily feed of new postings in Mexico, Colombia, Peru, Argentina, Chile and more.
- Labour market research: count remote, hybrid and onsite roles, contracts and required experience for any search.
Run it on Apify
- Open computrabajo-scraper on Apify and sign in, or make an Apify account.
- On the Input tab, fill in the fields listed below. The form opens with example values filled in.
- Click Start. Rows appear on the Output tab while the run works.
- Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
- 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
- Countries (
countries): Computrabajo sites to search; each search term runs on each of them. Options: Mexico, Colombia, Argentina, Peru, Chile, Ecuador, Venezuela, Guatemala, Costa Rica, Dominican Republic, Panama, El Salvador, Honduras, Bolivia, Paraguay, Uruguay, Nicaragua, Puerto Rico. Default:["mx"]. - Search terms (
keywords): Job titles or words such as contador, vendedor or desarrollador python. One search per term; leave empty with a city to list every posting there. - City or region (
location): Optional city, state or region such as Monterrey, Bogotá, Lima or Nuevo León. Applies to every search term. - Posted within (
postedWithin): Only postings published or updated in that period. Options: Any time, Last 24 hours, Last 3 days, Last 7 days, Last 15 days, Last 30 days. Default:any. - With a salary only (
salaryOnly): Only postings that show a salary (not "A convenir"). Default:false. - Remote or hybrid only (
remoteOnly): Only postings marked remote or hybrid (presencial y remoto). Default:false. - Search URLs (
searchUrls): Search result pages copied from your browser, for example https://mx.computrabajo.com/trabajo-de-contador-en-monterrey . - Include posting details (
includeDetails): Read each posting's page for the date first posted, contract type, schedule, industry, salary value, education, experience, languages, skills and the description. Switch it off for a faster run that reads only the search pages. Default:true. - 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.
{
"countries": [
"mx"
],
"keywords": [
"contador"
],
"location": "Monterrey",
"includeDetails": true,
"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.
# pip install apify-client
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN") # your own API token, from the Apify Console
run_input = {
"countries": ["mx"],
"keywords": ["contador"],
"location": "Monterrey",
"includeDetails": True,
"maxItems": 20,
}
run = client.actor("v0iddo/computrabajo-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)Limits
- One search runs per country and search term, with the city or region you chose. Pasted search URLs are read as they are. Postings are unique by ID across the whole run.
- salaryText is the salary as the posting shows it. salaryMin, salaryMax (the same value: Computrabajo shows one figure), salaryCurrency and salaryInterval come from the posting page with details on and are read from salaryText otherwise. A salary "A convenir" (to be agreed) is salaryHidden with no figures.
- postedDate is the date of the posting's last publication or update, from the search page's "Hace 3 horas" or "Ayer", the order Computrabajo lists results in. firstPostedDate, with details on, is the date the posting first went up. Posted within, with a salary only and remote only are applied to the rows read; Computrabajo's own filters are not used.
- contractType, schedule, industry, education, skills and the posting's own text stay in Spanish as published; workMode is onsite, hybrid or remote and employmentType is the posting's schema.org value.
- confidentialEmployer is true when the company is shown without its name and profile ("Importante empresa del sector"). promoted marks a highlighted posting ("Empleo destacado") and urgent one marked "Se precisa Urgente". The age requirement some postings carry is not collected.
- E-mail addresses, phone numbers and handles are removed from the text.
- Not affiliated with Computrabajo or Redarbor.
- 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 Computrabajo, cookies or an API key?
No. The actor reads only what every visitor of Computrabajo can see, without logging in. You only need an Apify account to start it.
How many results can one run return?
Up to 10,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