Gupy Jobs Scraper: postings + the hiring company's registry record

By LatSouth. Scrape Gupy job postings (Brazil) and get each posting normalized plus the hiring company's record from the official company registry, with the match method and a confidence score. Or switch to hiring_companies mode and get one row per company that is hiring (open jobs, areas, seniority, locations, latest posting): a ready-made hiring-intent signal for B2B prospecting.

Gupy is the ATS behind the career pages of thousands of Brazilian companies (portal.gupy.io, about 80,000 open postings). Each company declares its own website on its Gupy career page, so the registry match is by domain first.

Board	Gupy (Brazil)
Registry BR	Receita Federal CNPJ open data (CNPJ, legal name, size, CNAE activity, verified website)
Price	US$0.002 per posting (job-result) · US$0.008 per hiring company (company-result)
Measured (real sample, N = 438 postings)	40.6% of named companies matched · precision 39/40 on a manual review

Use cases

• Hiring-intent prospecting: companies opening sales, data or engineering roles this week, with tax id, size and activity, ready for outbound or account scoring.
• Recruiting and HR-tech market maps: who hires what, where, by seniority and workplace type.
• Labour-market research: postings by city, area and date, deduplicated across keywords.

Input examples

Postings of the last 7 days

{"keywords": ["analista de dados", "engenheiro de dados"], "posted_within_days": 7, "max_results": 200}

Who is hiring (one row per company)

{"mode": "hiring_companies", "keywords": ["vendas", "sdr", "executivo de contas"], "max_jobs_scanned": 1000, "max_results": 200}

Field	What it does
mode	jobs (default): one row per posting. hiring_companies: postings grouped by company.
keywords	One search per keyword; results deduplicated. Empty = newest postings.
workplace_types	remote, hybrid, onsite (empty = all)
state	Brazilian UF (SP or Sao Paulo)
city	City as written on the board
posted_within_days	Only postings of the last N days
max_results	Rows to return (postings or companies); you pay per row. Default 25: an empty input {} returns 25 postings (about US$0.05), each with the hiring company's registry match in company; company rows (company-result) come only in hiring_companies mode
max_jobs_scanned	hiring_companies mode: postings read before grouping (scanning is free)
enrich	Registry join (default true)
include_description	First 600 characters, HTML removed, e-mails and phone numbers scrubbed
proxyConfiguration	Optional Apify Proxy (default off), datacenter only: a RESIDENTIAL group or custom proxy URLs are rejected. IP location and request spreading only, no captcha or bot-challenge solving

Output

Posting row (jobs mode): board, country, job_id, url, title, company_name (as shown on the board; null when confidential), company_board_id, company_website, city, state, workplace_type, contract_type, seniority (from the title only), published_at, salary fields (only when the board shows a salary), description, accepts_pwd, scraped_at and company. Fields a board does not publish are null.

Company row (hiring_companies mode): company_name, career_page_url, company_website, n_open_jobs, titles_sample, seniority_mix, workplace_mix, contract_mix, locations, most_recent_posting_at, job_urls_sample and company. Sorted by open jobs, then latest posting.

company block: match_status (matched, low_confidence, ambiguous with candidate_tax_ids, not_found, skipped), match_method, match_confidence (0-1), match_note, then the registry record: tax_id, tax_id_formatted, legal_name, trade_name, legal_form, status, activity code and label (local + ISIC), size, region, city, website, data_as_of, source, source_license.

How the registry match works on Gupy

Order of evidence: 1. the website the company declares on the board -> registry companies whose HTTP-verified website or corporate e-mail uses that domain (exact, then parent domain); 2. otherwise the exact company name, accepted only when exactly one registry company carries it. A name or domain shared by several registry companies is never guessed: ambiguous with the candidates. Confidential postings, and employers whose name is a private person's name (sole traders), are returned without a company name and are never matched. Many postings are published by recruiting agencies: the match is then the agency (the poster).

Data and compliance

Company data only. E-mail addresses, phone numbers and personal ids are scrubbed from descriptions; recruiter and candidate data are never collected. No login, no captcha, at most 2 requests per second. Registry records carry their official source and licence (company.source, company.source_license).

Pricing

Pay per event: US$0.002 per posting and US$0.008 per hiring company, plus the standard Apify actor start. The run stops at your spending limit. Scanning postings in hiring_companies mode is free; you pay per company row.

Never charged for a broken run: if Gupy blocks the run or changed its layout (the first search page cannot be read and is not the board's own "no results" page), the run fails with that reason and nothing is charged; a search that simply has no postings succeeds with 0 rows. With enrich: true and the registry unreachable, the run fails before reading the board. In jobs mode rows are pushed as they are ready (the first ones after the first page).

More boards

Need several boards in one run (Gupy, InfoJobs, Catho, Computrabajo, Bumeran, OCC)? Use LATAM Jobs & Hiring Signals: same output, all boards.

Em português

Raspe vagas do Gupy e receba, em cada vaga, o CNPJ da empresa que está contratando (razão social, porte, CNAE, site verificado) com método e confiança do match. No modo hiring_companies, uma linha por empresa contratando (vagas abertas, áreas, senioridade, cidades): sinal de intenção para prospecção B2B. Vagas confidenciais e empregadores pessoa física saem sem nome e sem match. Preço: US$0,002 por vaga e US$0,008 por empresa.