← data exports  /  apify actor

Computrabajo Salary Benchmark by Job Title and Country

how to get the data with our Apify actor computrabajo-salary-benchmark

Get a salary benchmark for any job title from Computrabajo postings in 18 Latin American countries: monthly median, quartiles and range in local currency, share of postings showing pay, listings, top employers, cities, work modes and contract types. One price per benchmark.

on apify
v0iddo/computrabajo-salary-benchmark
category
jobs, automation
build
0.1.3, built 2026-11-15
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:

  • Job title (jobTitle)
  • country
  • Place (location)
  • Listings (listingsOnSite)
  • Salaries (salariesUsed)
  • P25 (salaryP25)
  • Median (salaryMedian)
  • P75 (salaryP75)
  • currency
  • Show pay % (salarySharePercent)
  • Search (searchUrl)

Run it on Apify

  1. Open computrabajo-salary-benchmark on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. 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

  • Job titles (jobTitles): Job titles as postings name them, in Spanish, one per line, for example contador, vendedor or desarrollador python. Each title gets its own benchmark in each country.
  • Countries (countries): Computrabajo sites to read; each job title gets one benchmark in 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"].
  • City or region (location): Optional city, state or region such as Monterrey, Bogotá, Lima or Nuevo León, for a benchmark of that place. With Mexico, the default, as the only country, a large city of another country (Bogotá, Lima, Santiago) searches that country's site.
  • Postings read per benchmark (listingsPerBenchmark): Postings read for each benchmark, the newest first (20 a page). More postings give a steadier median; the price per benchmark stays the same. Default: 200.
  • Posting pages read per benchmark (detailPages): Posting pages read for each benchmark, spread over the postings read, for contract types, schedules, experience asked, education and skills. 0 skips them for a faster run. Default: 20.
  • Matching titles only (titleMustMatch): Count only postings whose title holds every word of the job title (accents, case and the a or o ending ignored: enfermera counts Enfermero/a). Switch it off to count every posting Computrabajo's search returns, which after its first pages lists related and unrelated jobs too. Default: true.
  • Search URLs (searchUrls): Computrabajo search result pages copied from your browser, one benchmark each, for example https://mx.computrabajo.com/trabajo-de-contador-en-monterrey .
  • 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.

example inputjson
{
  "jobTitles": [
    "contador"
  ],
  "countries": [
    "mx"
  ],
  "location": "Monterrey",
  "listingsPerBenchmark": 100,
  "detailPages": 10,
  "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.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "jobTitles": ["contador"],
    "countries": ["mx"],
    "location": "Monterrey",
    "listingsPerBenchmark": 100,
    "detailPages": 10,
    "maxItems": 20,
}
run = client.actor("v0iddo/computrabajo-salary-benchmark").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • Reads Computrabajo's public search pages and a sample of posting pages, the same pages as our Computrabajo Scraper. Its robots.txt is obeyed: the site's own filter parameters are not used. Contact details are not collected.
  • Salaries are monthly, in the currency most of the search's postings use. A range counts as its midpoint; yearly pay is divided by 12, pay every two weeks doubled and weekly pay multiplied by 52 / 12. Daily and hourly pay, a figure without a period, another currency, filler figures such as 11,111 or 9,999,999 and outliers (under a fifth or over five times the median) are left out and counted in salariesLeftOut.
  • salarySharePercent is the share of the postings counted that show a salary at all; many employers write "A convenir" (to be agreed).
  • By default only postings whose title holds the words of the job title are counted (listingsCounted; titleMatchPercent is their share of the postings read): Computrabajo's search lists the closest titles first and then related and unrelated jobs, and reading stops after 3 pages without a matching title. listingsOnSite is the count in Computrabajo's own heading for the search.
  • topEmployers leaves out confidential employers ("Importante empresa del sector") and employers listed under what reads as a person's name, and gives an employer's median pay from 3 salaries.
  • contractTypes, schedules, experienceYearsMedian, educationLevels and topSkills come from the posting pages read (detailPages) and stay in Spanish as published.
  • A worked example with real figures: https://voidd0.github.io/data/computrabajo-salaries-2026-11/ shows 36 benchmarks (6 job titles in 6 countries) read with this method in November 2026, with the CSV; a Spanish edition is at https://voidd0.github.io/data/computrabajo-salarios-2026-11/ .
  • Not affiliated with Computrabajo or Redarbor.
  • On an Apify account without a paid plan a run returns up to 1 result; on any paid Apify plan it returns up to Maximum results.
  • 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 the developer a short usage record: the number of results, success or the kind of error, paid plan or not, how it was started and a hashed account code, so repeat runs count once. Nothing from your input or results is sent.

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 1,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