Catho job listings for Brazil as JSON: search by job title, then the full posting with salary in BRL
- endpoints
- 2
- credit per call
- 1
The Catho API returns job listings from Catho (catho.com.br), a Brazilian job board, as JSON: a search by job title that lists open postings with their Catho job id and link, and the full posting with company, street, city, state, salary range in Brazilian reais where Catho shows it, contract type, remote flag, posting date and the full description.
/catho/v1
- POST/catho/v1/jobs/search1 credit
- POST/catho/v1/jobs/detail1 credit
≈ 1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Catho API
2 of 2 endpoints, ready to run
Search Catho job listings by job title
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Catho endpoints does ReefAPI ship?
2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
jobs/search
1 crSearch live Catho job listings by keyword and city → jobs[] with title, company, location, po…
- required
- —
- optional
- keyword, query, location, max_pages, max_results, page_size
jobs/detail
1 crOne Catho posting in full by job_url (a catho.com.br/vagas/.
- required
- —
- optional
- job_id, job_url, apply_url
Every parameter, every allowed value →
Missing a Catho endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Catho API works
Catho is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 746 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a job title to full Catho postings with salary
Search Catho for a job title to get the list of open postings, then open each posting you need for the company, place, salary and description.
{"keyword": "analista", "max_pages": 1}20 postings on 2026-11-21 (0.9 s), each with Catho's job_id, a title read from the posting link and the posting URL (apply_url). Search rows carry no company, city, date or salary; meta.completeness_pct said 50.0 and lists the fields it scored.
{"job_url": "<apply_url from a row>"}The full posting in about 1 second: title, company, street, city, state, country, salary range in BRL, contract type ("CLT (Efetivo)"), remote flag, posting date and the full description in Portuguese. Old calls to POST /global-jobs/v1/... with platform catho keep working unchanged.
A dated list of open Catho postings in Brazil for one job title, with employer, city and state, and the salary range wherever Catho publishes one.
curl -X POST https://api.reefapi.com/catho/v1/jobs/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"analista","max_pages":1}'{
"ok": true,
"data": { … },
"meta": {
"api": "catho",
"endpoint": "jobs/search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Catho field actually contains
Fields that read differently from how they look. Each row was measured on live Catho data on 2026-11-21.
| Field | What it holds |
|---|---|
| title (search row) | Read from the posting link, so title-cased and without accents: "Analista De Ecommerce", "Desenvolvedor Full Stack Pleno". jobs/detail returns the title as Catho prints it ("Analista Fiscal"). |
| job_id | Catho's own posting number (39343322), the last part of the posting link. Unique within Catho, not across job boards. |
| apply_url / source_url | The posting link on catho.com.br (https://www.catho.com.br/vagas/<slug>/<job_id>/). Pass apply_url back as job_url to jobs/detail. |
| company_name | The employer as Catho shows it ("DENTOFLEX INP"). When Catho hides the employer, jobs/detail returns "Confidential employer". |
| location_city, location_state, location_country, location_raw | From jobs/detail only: São Paulo, SP, Brasil, and location_raw with the street ("Rua Marquês de Maricá, SP, Brasil"). |
| salary_min, salary_max, salary_currency, salary_text | The range Catho prints, in BRL: 3001, 4000, BRL, "3001-4000 BRL". salary_source is detail_ld when read from the posting, unpublished when the employer gave none. |
| employment_type | Catho's contract type in Portuguese, e.g. "CLT (Efetivo)" (a permanent employment contract under Brazilian labour law). |
| posted_at | ISO date stamped at the end of the day ("2026-11-19T23:59:59Z"), so it orders postings by day, not by hour. |
| meta.completeness_pct | How many of job_id, title, company_name, location_raw, posted_at and apply_url the search rows fill: 50.0 on Catho search, because three of the six exist only in jobs/detail. |
Descriptions, contract types and titles are in Portuguese, as the employer wrote them. Nothing is translated or converted.
Catho coverage, measured
Every number below comes from live Catho calls on 2026-11-21: two searches and one full posting.
Brazil only (catho.com.br). Postings are written in Portuguese, so Portuguese job titles find them: "analista" and "desenvolvedor" each returned a full first page of 20 postings. Brazil's other job board, Gupy, has its own page: /gupy-api.
job_id, title, apply_url, source_url and source_platform on 20 of 20 rows. The title comes from the posting link, so it is title-cased and without accents ("Analista De Ecommerce"). No company, city, posting date or salary in search rows.
"Analista Fiscal" (job 39343322): company DENTOFLEX INP, Rua Marquês de Maricá, São Paulo, SP, Brasil; salary 3,001 to 4,000 BRL; contract CLT (Efetivo); remote false; posted 2026-11-19; full description in Portuguese.
salary_min, salary_max and salary_currency (BRL) when Catho prints a range, with salary_source detail_ld. When it does not, salary_source says unpublished and the numbers are empty. No currency conversion.
0.8 to 0.9 s for a one-page search, 0.9 s for a full posting.
Search does not narrow by city on Catho: the location parameter is not applied to Catho results, so filter on location_city and location_state from jobs/detail. Catho dates postings to the end of the day (23:59:59Z), not the hour. A posting whose employer Catho hides comes back with company "Confidential employer".
What people build with Catho
The jobs this data is most often used for.
Track open Catho postings in Brazil for a job title, e.g. every new "analista fiscal" role.
Collect the salary ranges Brazilian employers publish on Catho, in BRL, for pay benchmarks.
Build a Brazilian job board or alert from Catho postings with company, city and state.
Measure which Brazilian employers hire for a role, by state, from the full postings.
endpoints
credit per call
What Catho data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 746 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/catho/v1/jobs/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"analista","max_pages":1}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/catho/v1/jobs/search",
headers={"x-api-key": REEF_KEY},
json={
"keyword": "analista",
"max_pages": 1
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Catho.
Is there a Catho API?▾
Yes. The catho API on ReefAPI reads catho.com.br's public job search and posting pages and returns them as JSON, no Catho account needed: jobs/search lists open postings for a job title, jobs/detail returns one posting in full with company, city, state, salary in BRL, contract type and description.
Which country does it cover?▾
Brazil. Catho is a Brazilian job board and every posting it lists is in Brazil; location_country reads Brasil. For India see the naukri API.
Should I search in English or Portuguese?▾
Portuguese. Catho postings are written in Portuguese, and the keyword is matched against Portuguese job titles: search "analista" or "desenvolvedor", not "analyst" or "developer". On 2026-11-21 "analista" and "desenvolvedor" each returned a full first page of 20 postings.
Why does a search row have only a title and a link?▾
Because Catho's result page lists only that. On 2026-11-21 all 20 rows of an "analista" search carried job_id, title, apply_url, source_url and source_platform, and meta.completeness_pct was 50.0. Company, city, state, date and salary are on the posting itself: pass the row's apply_url as job_url to jobs/detail.
Does it return the salary?▾
When Catho prints one. jobs/detail returns salary_min, salary_max and salary_currency in Brazilian reais (BRL), e.g. 3,001 to 4,000 BRL on the Analista Fiscal posting measured on 2026-11-21. When the employer published no salary, salary_source says unpublished. Nothing is converted to another currency.
Can I filter Catho jobs by city?▾
Not in the search call: Catho search results are national and the location parameter is not applied to them. Each posting from jobs/detail carries location_city and location_state (e.g. São Paulo, SP), so filter on those.
How many jobs does one search return?▾
About 20 per result page (20 on each search measured on 2026-11-21). max_pages sets how many pages are read (default 10) and max_results caps the total. Search is billed per 25 jobs returned; jobs/detail is one call per posting.
How fast is it?▾
On 2026-11-21 a one-page search answered in 0.8 to 0.9 seconds and a full posting in 0.9 seconds.
Do old global-jobs calls still work?▾
Yes. POST /global-jobs/v1/jobs/search and /jobs/detail with platform catho keep working unchanged. The call for Catho alone is POST /catho/v1/jobs/search and POST /catho/v1/jobs/detail, with the same parameters minus platform.
What is the Catho API?▾
Catho API is a ReefAPI endpoint group for brazil job listings from catho.com.br: search by job title, then each posting in full with company, city, state and salary in brl. It returns live JSON through POST requests under /catho/v1.
Is the Catho API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Catho calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Catho login or account?▾
No login to Catho is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Catho data?▾
The page example is captured from a live jobs/search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Catho API use?▾
Catho actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
36 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Catho, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 745 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-21.