Gupy Search Scraper
Pricing
from $2.99 / 1,000 gupy job records
Gupy Search Scraper
Scrape job listings from Gupy.com.br, a leading Brazilian job platform. Extract job titles, companies, locations, salary ranges, and descriptions for Brazilian recruitment.
Pricing
from $2.99 / 1,000 gupy job records
Rating
0.0
(0)
Developer
Jobs API
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
11 days ago
Last modified
Categories
Share
Gupy Jobs Search Scraper
Search public Gupy job listings through the official Gupy employability API and enrich each candidate from its public career detail page.
Input
- query: search phrase, default desenvolvedor.
- location: optional location filter sent to the API and checked against detail output.
- maxItems: maximum verified records, 1-500, default 3.
- maxPages: maximum API pages, 1-25, default 5.
Runtime, retry, proxy, fixture, raw-payload, user-agent, and debug controls are intentionally not public inputs. Requests are sequential ordinary direct HTTPS with fixed internal timeout and spacing.
Output
The Actor emits one dataset row per unique, detail-verified job. Rows include stable position and jobId values, canonical Gupy URLs, listing/detail receipts, company and location data, readable sectioned descriptions, requirements, responsibilities, benefits, skills, dates, process stages, application URL when explicitly published, and source metadata. Contact emails and phone numbers are redacted; raw source payloads are never emitted.
Platform run status (SUCCEEDED or FAILED) is separate from extraction resultStatus (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). Summary counts include only Dataset writes that resolved successfully. Confirmed source access denials stop requests and discard staged jobs; ambiguous empty responses remain DEFERRED, while NO_DATA requires a successful, hashed response with an explicit empty-results signal. Diagnostics and request receipts stay in the key-value store, outside the Dataset.
Offline validation
npm run validate:dataset reads the existing local storage/ output. Use it only when local storage validation is in scope and the selected data is known to be safe to inspect.
The dataset validator checks lifecycle status and count reconciliation, confirmed empty or blocked evidence, and each row's source receipts, identity, readable detail, completeness, and Dataset schema fields.
