Torre Jobs & Recruiters Scraper: Tech Jobs + Hiring Contacts

What it does

Open job posts from Torre (torre.ai) with the company person who posted them, the visible hiring team, the company website and domain, salary, skills and remote policy. A second mode returns the recruiters themselves, one row per person, with their public Torre profile.

{
  "rowType": "job",
  "opportunityId": "AbCd1234",
  "url": "https://torre.ai/post/AbCd1234-acme-labs-senior-backend-engineer",
  "title": "Senior Backend Engineer",
  "status": "open",
  "remote": true,
  "countries": ["Colombia", "Mexico"],
  "compensation": { "code": "range", "currency": "USD", "min": 4000, "max": 6000, "periodicity": "monthly" },
  "organization": { "name": "Acme Labs", "size": 40, "website": "https://www.example.com", "domain": "example.com" },
  "domain": "example.com",
  "postedBy": { "name": "Jane Doe", "headline": "Talent Partner at Acme Labs", "profileUrl": "https://torre.ai/janedoe" },
  "members": [{ "name": "John Roe", "headline": "Co-Founder & CTO", "isManager": true }],
  "postedByTorre": false,
  "talentSeekerInactive": false,
  "emailPattern": { "domain": "example.com", "pattern": "first.last", "confidence": 0.1, "inferred": true, "mxValid": true, "catchAll": null },
  "detailScraped": true,
  "scrapedAt": "2026-10-01T23:30:00.000Z"
}

Why this one

Use cases

• Find open remote tech jobs with a salary range in USD, time zones and the person who posted them.
• Map companies hiring now, with website, domain, team size and the visible hiring team.
• Enrich an existing list of Torre job URLs with the full page, team and company domain.
• Build a salary dataset from Torre's structured compensation, including hourly USD equivalents.

Input

Every field has a default, and the defaults are deliberately small so a first run is cheap enough to inspect before you commit to a sweep. This table mirrors the Actor's own input schema field for field.

Output and fill rates

A field being in the schema is not the same as it having a value. The percentages below were counted on real runs; the sample sizes are in Measurements. Anything not listed here is not promised.

Every key is always present. A field that exists but is empty comes back as explicit null, so a parser never has to guess.

Datasets

Different record types go to different datasets, so the main table never carries columns that are blank on most rows.

Pricing

Pay per delivered result. Charges are applied as each row is produced rather than in a lump at the end, so an aborted run bills only for what it actually gave you.

Measurements

Each figure is shown with the method that produced it. A benchmark without a method is a marketing claim wearing a number's clothes.

What it will not do

Stated plainly so you can judge fit before spending anything.

• Recruiter fields apply mainly to the 41.8% of open posts that companies publish themselves; aggregated posts have no company recruiter.
• Salary minimum is filled on 40.9% of 330 posts: 63.8% of company-published posts and 24.5% of aggregated ones.
• On-site and hybrid jobs are searched around the main cities of each country, about 30–50 km each, so on-site coverage is by city and not exhaustive.
• Since 2 October 2026 Torre only answers searches made for a person; the Actor uses a public Torre profile as that context with its skills and preferences removed. Results come in Torre's relevance order, not by date.
• The email pattern is almost always an inferred guess: all 45 domains measured on 1 October 2026 had no email evidence.
• torre.ai/robots.txt disallows `/api/` and Torre's terms prohibit scraping; the full job page and profile reads use `/api/` paths.

Privacy

• Recruiter rows and the `postedBy` and `members` fields are personal data about named people who post jobs or appear on a hiring team.
• People whose Torre profile places them in the EU, EEA, UK or Switzerland are excluded by default; including them requires `includeEuRecruiters` and a lawful basis.
• Torre publishes no personal emails, and the Actor never guesses addresses outside the company domain; personal-domain emails in descriptions are hidden unless `includePersonalEmails` is on.
• Team members Torre hides on the public job page and screening messages written by candidates are never delivered.
• No email is ever sent and no mail server is probed.
• Removal requests: privacy@actorstack.dev

See also the data removal process.

Guides for this Actor

• Torre jobs and recruitersTorre names the person behind a job post. What the Torre Actor collects about those people, who is excluded by default, and what Torre's robots.txt and terms say.