Gupy job listings for Brazil as JSON: search by job title and state, then the full posting from the company's career page
The Gupy API returns job listings from Gupy, the Brazilian recruiting platform whose job portal (portal.gupy.io) lists the open postings of the companies that hire through it, as JSON.
- endpoints
- 2
- credit per call
- 1
≈ 1 credit per call≈ $1/1,000 calls1,000 free credits, no card
2 active endpoints. Every call is 1 credit.
- POST/gupy/v1/jobs/search1 credit
- POST/gupy/v1/jobs/detail1 credit
Run 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.
Gupy API
2 of 2 endpoints, ready to run
Search Gupy 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 Gupy endpoints does ReefAPI ship?
2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Every parameter, every allowed value →
Missing a Gupy endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Gupy API works
Gupy 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 Gupy postings
Search Gupy for a Portuguese job title, optionally in one state, then open the postings you need for the full description with responsibilities and requirements.
{"keyword": "desenvolvedor", "max_pages": 3}60 postings in 3.0 s on 2026-11-22, each with job_id, title, company_name, description_text, posted_at, apply_url, employment_type, industry and remote. Search is billed 1 credit per 25 jobs returned.
{"keyword": "enfermeiro", "location": "São Paulo", "max_pages": 2}40 nursing postings in the state of São Paulo.
{"job_url": "<apply_url from a row>"}The full posting from the company's career page in 0.8 to 1.3 s, 1 credit. Old calls to POST /global-jobs/v1/... with platform gupy keep working unchanged.
A dated list of open Gupy postings in Brazil for one job title, with employer, state, remote flag, contract type and skills, and the full text of each posting you open.
curl -X POST https://api.reefapi.com/gupy/v1/jobs/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"desenvolvedor","max_pages":1}'{
"ok": true,
"data": { … },
"meta": {
"api": "gupy",
"endpoint": "jobs/search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Gupy field actually contains
Fields that read differently from how they look. Each row was measured on live Gupy data on 2026-11-22.
| Field | What it holds |
|---|---|
| job_id | Gupy's own posting number (12838079), the last part of a <company>.gupy.io/jobs/<id> link. Unique within Gupy, not across job boards. |
| title | The job title as the employer wrote it, often in capitals ("DESENVOLVEDOR JAVA SR"). The keyword is matched literally against it. |
| company_name, company_logo_url | The hiring company (Globalweb, FCamara). The logo was on 18 of 20 rows. |
| description_text | The posting text, on 20 of 20 search rows. jobs/detail returns the full posting from the company's career page, with responsibilities and requirements. |
| remote, location_state | remote is true for remote postings, which carry no state; location_state was on 10 of 20 "desenvolvedor" rows. location in the search narrows by state: "enfermeiro" in São Paulo gave 40 postings for 2 pages. |
| employment_type | Gupy's own contract code as Gupy writes it, e.g. vacancy_legal_entity. Passed through, not translated. |
| skills, experience_level, industry | skills on 19 of 20 rows, industry on 20 of 20, experience_level only on 4 of 20: many employers leave it empty. |
| posted_at, apply_url | The publication date (job 12838079: 2026-11-20) and the posting link (<company>.gupy.io/job/<code>), which jobs/detail accepts as job_url. |
| meta.source_total | Gupy's own count, which stops at 100 when there are more: it is not the full number of open postings. |
| meta.keyword_relaxed_to | Set when a phrase found nothing and the search retried with its most distinctive word: "python developer" was relaxed to "python" (1 posting). |
Titles, descriptions and contract codes are in Portuguese or Gupy's own codes, as the employer and Gupy wrote them. Nothing is translated.
Gupy coverage, measured
Every number below comes from live Gupy calls on 2026-11-22.
Brazil only. Postings are written in Portuguese and Gupy matches the phrase literally in the job title: "enfermeiro" returned 200 postings, English "Nurse" returned 0 (NOT_FOUND).
"desenvolvedor": max_pages 1 → 20 postings in 1.5 s, max_pages 3 → 60 in 3.0 s. "enfermeiro" with the defaults (10 pages of 20) → 200 postings in 8.6 to 11.8 s. "analista" with page_size 50 → 50 in 2.7 s.
location takes a state such as São Paulo: "enfermeiro" in São Paulo with max_pages 2 returned 40 postings.
On 20 "desenvolvedor" rows: job_id, title, company_name, description_text, posted_at, apply_url, employment_type, industry and remote on 20 of 20; skills on 19; company_logo_url on 18; location_state on 10 (remote postings have no state); experience_level on 4.
Job 12838079 "DESENVOLVEDOR JAVA SR" at Globalweb: remote, posted 2026-11-20, employment_type vacancy_legal_entity.
https://fcamara.gupy.io/jobs/12916729 returned "Desenvolvedor Fullstack Java Especialista" at FCamara with the full description, responsibilities and requirements included, in 0.8 to 1.3 s. A search row's apply_url (<company>.gupy.io/job/<code>) works as job_url too.
A phrase that matches no title is retried with its most distinctive word and the response says so: "python developer" was relaxed to "python" (1 posting), stated in meta.keyword_relaxed_to.
Gupy's own result count stops at 100 when there are more (meta.source_total 100), so it is not the full number of open postings. Remote postings carry no state.
What people build with Gupy
The jobs this data is most often used for.
endpoints
credit per call
Track open Gupy postings in Brazil for a job title, e.g. every new "desenvolvedor java" role.
Count remote versus on-site postings for a role from Gupy's remote flag.
Build a Brazilian job board or alert from Gupy postings with company, state, contract type and skills.
Measure which Brazilian employers hire for a role, by state, from Gupy and Catho together.
What Gupy 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/gupy/v1/jobs/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"desenvolvedor","max_pages":1}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/gupy/v1/jobs/search",
headers={"x-api-key": REEF_KEY},
json={
"keyword": "desenvolvedor",
"max_pages": 1
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Gupy.
Is there a Gupy API?▾
Yes. The gupy API on ReefAPI reads Gupy's public job portal and the companies' gupy.io career pages and returns them as JSON, no Gupy account needed: jobs/search lists open postings for a job title, jobs/detail returns one posting in full.
Which country does it cover?▾
Brazil. Gupy is a Brazilian recruiting platform and its job portal lists Brazilian postings. Filter by state with location, e.g. São Paulo.
Should I search in English or Portuguese?▾
Portuguese. Gupy matches the phrase literally in the job title: on 2026-11-22 "enfermeiro" returned 200 postings and "Nurse" returned 0 (NOT_FOUND).
What does a search row contain?▾
job_id, title, company_name, description_text, posted_at, apply_url, employment_type, industry and remote on 20 of 20 "desenvolvedor" rows; skills on 19, company logo on 18, state on 10 (remote postings have none), experience level on 4.
How many jobs does one search return?▾
page_size jobs per page (20 by default) for max_pages pages (10 by default), capped by max_results: 200 postings for "enfermeiro" with the defaults, 60 for "desenvolvedor" with max_pages 3, 50 for "analista" with page_size 50. Search is billed 1 credit per 25 jobs returned.
How do I get the full posting?▾
Pass a <company>.gupy.io/jobs/<id> link, or a search row's apply_url, as job_url to jobs/detail: https://fcamara.gupy.io/jobs/12916729 returned "Desenvolvedor Fullstack Java Especialista" at FCamara with responsibilities and requirements in about a second, for 1 credit.
How fast is it?▾
On 2026-11-22: 1.5 seconds for 20 postings, 3.0 seconds for 60, 8.6 to 11.8 seconds for 200; 0.8 to 1.3 seconds for a full posting.
How is it different from Catho?▾
Both are Brazilian job boards. Gupy search rows already carry the company, description, date and contract type; Catho search rows carry only a title and a link, and the rest comes from its detail call. Catho has its own page: /catho-api.
Do old global-jobs calls still work?▾
Yes. POST /global-jobs/v1/jobs/search and /jobs/detail with platform gupy keep working unchanged. The call for Gupy alone is POST /gupy/v1/jobs/search and POST /gupy/v1/jobs/detail, with the same parameters minus platform.
What is the Gupy API?▾
Gupy API is a ReefAPI endpoint group for brazil job listings from the gupy job portal: search by job title and state, each row with company, remote flag, contract type, skills and date, then the full posting. It returns live JSON through POST requests under /gupy/v1.
Is the Gupy API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Gupy calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Gupy login or account?▾
No login to Gupy 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 Gupy 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 Gupy API use?▾
Gupy 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 Gupy, 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-22.