Gupy Jobs Scraper: Brazil Job Vacancies

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

• title
• company
• city
• state
• Job type (jobTypeLabel)
• Work mode (workplaceType)
• Reason (hiringReason)
• Posted (publishedAt)
• Apply by (applicationDeadline)
• Posting (url)

What people use it for

• Brazilian hiring signals: see which large employers open new positions or replace staff, by state and city.
• Recruitment agencies and HR: follow the hiring steps, job types and deadlines of the employers you serve.
• Job boards and newsletters: a daily feed of new Brazilian postings with their posting and deadline dates.
• Labour market research: count remote, hybrid and onsite roles, internships and contractor (PJ) roles.

Run it on Apify

1. Open gupy-scraper on Apify and sign in, or make an Apify account.
2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
3. Click Start. Rows appear on the Output tab while the run works.
4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

• Search terms (keywords): Job titles or words such as analista, desenvolvedor or vendedor. One search per term; leave empty to list every posting that matches the other filters.
• State (state): Only postings in this Brazilian state. Options: Any state, Acre, Alagoas, Amapá, Amazonas, Bahia, Ceará, Distrito Federal, Espírito Santo, Goiás, Maranhão, Mato Grosso, Mato Grosso do Sul, Minas Gerais, Pará, Paraíba, Paraná, Pernambuco, Piauí, Rio de Janeiro, Rio Grande do Norte, Rio Grande do Sul, Rondônia, Roraima, Santa Catarina, São Paulo, Sergipe, Tocantins.
• City (city): Only postings in this city, written as on Gupy, for example Campinas or Belo Horizonte.
• Work mode (workplaceTypes): Only these work modes. Leave empty for all. Options: Onsite, Hybrid, Remote.
• Job types (jobTypes): Only these job types. Leave empty for all. Options: Permanent (Efetivo), Internship (Estágio), Apprentice (Aprendiz), Trainee, Temporary (Temporário), Contractor (Pessoa Jurídica), Freelancer, Self employed (Autônomo), Talent pool (Banco de Talentos), Associate (Associado), Outsourced (Terceiro), Intermittent (Intermitente), Lecturer (Docente), Summer job, Volunteer (Voluntário), Partner (Sócio).
• Companies (companies): Only postings of these employers, by the name their Gupy career page shows, for example Stefanini Group or Raízen.
• Open to people with disabilities only (pwdOnly): Only postings marked as open to people with disabilities (PcD). Default: false.
• Posted within (postedWithin): Only postings published in that period. Options: Any time, Last 24 hours, Last 3 days, Last 7 days, Last 15 days, Last 30 days. Default: any.
• Include posting details (includeDetails): Read each posting's page for the description, responsibilities, requirements and nice to have as separate texts, the full address, the hiring steps, the reason for the opening and the expiry date. Switch it off for a faster run that reads only the search. Default: true.
• Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
• Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

{
  "keywords": [
    "analista de dados"
  ],
  "state": "São Paulo",
  "includeDetails": true,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "keywords": ["analista de dados"],
    "state": "São Paulo",
    "includeDetails": True,
    "maxItems": 20,
}
run = client.actor("v0iddo/gupy-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

• One search runs per search term, job type, work mode and company you chose, with the state, city and disability filters on each. Postings are unique by ID across the whole run, newest first.
• company is the name of the employer's Gupy career page as the search shows it, which some employers fill with a slogan; companySubdomain is the career site's address (ccl for ccl.gupy.io) and companyName, with details on, the name on the career page.
• jobType is Gupy's job type (effective, internship, legal_entity ...) and jobTypeLabel its Portuguese label. hiringReason is staff_increase (a new position) or staff_replacement, as the employer filed it.
• descriptionText, responsibilities, requirements and niceToHave are the posting's own sections in Portuguese with details on; with details off descriptionText is the search's text of the posting, the sections run together.
• Gupy publishes no salaries in its search or posting data; a salary an employer writes into the text stays in the text.
• E-mail addresses, phone numbers and handles are removed from the text. Recruiter names are not collected.
• Not affiliated with Gupy.
• Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
• The actor reads only pages that the site's robots.txt leaves open to automated access.
• Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on Gupy, cookies or an API key?

No. The actor reads only what every visitor of Gupy can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 20,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

• ATS Jobs Scraper: Greenhouse, Lever, Workday, Ashby
• Workday Jobs Scraper: Salary, Dates, Remote
• All our scrapers on the Apify Store