Search Catho jobs

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

Job ads on Catho (Brazil) for a role or keyword and a city, with contract type and sort. Each result has the title, company, number of openings, city, salary text and publication date; site_filters echoes the filters the site applied. 20 per page. Filters: salary, work model (remote, hybrid, on site), publication date, job area and disability type; applied_filters and site_filters show what was applied.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Role or keyword (e.g. desenvolvedor, analista, vendedor). Example: desenvolvedor
location string City as in the site's URLs: name and state, e.g. sao-paulo-sp, rio-de-janeiro-rj, belo-horizonte-mg. Example: sao-paulo-sp
contract string The site's contract type ids, comma separated.
sort relevance | date Sort order.
page string Results page (1-based). Pass next_page back; it is null on the last page.
salary_min integer Monthly salary from (BRL): picks the site's salary range at or below it (2,000; 3,000 ... 10,000; 15,000; above 20,000).
salary_range integer The site's salary range id instead of salary_min: 3 up to R$ 2,000; 4 to 13 from R$ 2,000, 3,000, 4,000, 5,000, 6,000, 7,000, 8,000, 9,000, 10,000, 15,000; 14 above R$ 20,000.
work_model string remote, hybrid, presential (or remoto, hibrido, presencial), comma separated.
posted_within integer Only ads published in the last N days: 0 (today), 1, 2, 7, 15 or 30.
area string The site's job area ids, comma separated.
disability string The site's disability (PcD) type ids, comma separated: ads open to candidates with that disability.

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

Example

curl "https://api.api.sh/catho/v1/search?q=desenvolvedor" \
  -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.