Search Computrabajo jobs

GET https://api.api.sh/computrabajo/v1/search
1 credit / call jobs & b2b try it in the playground →

Job ads on Computrabajo (Latin America's largest job board, one site per country: Colombia, Mexico, Argentina, Peru, Chile, Ecuador and 12 more) for keywords, a region or city, or a category, with the site's filters: posting date, salary range, contract type, experience, working hours, disability-friendly and sort. Each result has the title, employer with its rating, location, salary, work modality, posting age and link; confidential ads show the site's generic employer text. facets lists every filter value with its count. 20 per page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
country ar | bo | cl | co | cr | do | ec | gt | hn | mx | ni | pa | pe | pr | py | sv | uy | ve Computrabajo country site (default co). Example: co
q string Keywords (job title or skill). Example: python
location string Region or city as in the site's URLs (e.g. bogota-dc, antioquia, jalisco, lima). Example: bogota-dc
category string Category slug when searching without q (e.g. informatica-y-telecom; see facets).
schedule full_time | part_time | hourly | internship Working hours.
posted 1 | 3 | 7 | 15 | 30 | 99 Only ads from the last N days (99 = urgent ads).
salary string Salary range value from the Salario facet (ranges differ by country).
contract string Contract type value from the Contrato facet (e.g. 5 indefinite term in Colombia).
experience string Experience value from the Experiencia facet (4 one year, 5 two years, 6 three to four years).
disability 1 | 0 1 = only ads open to people with disabilities.
sort relevance | date | salary Sort order.
page string Results page (1-based). Pass next_page back; it is null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/computrabajo/v1/search?country=co" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.