Torre Scraper
Pricing
Pay per usage
Torre Scraper
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Acquisition Automation Co.
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share

Torre Candidate Sourcing Tool: Scrape 2.6M Talent Profiles
Search 2,699,211 Torre profiles and pull 28 fields per candidate, with 7 filters that Torre's own API actually honours. Every row carries name, headline, location, verified status, remote availability, up to 306 skills, pay expectations and what the person is open to. No login, no API key, no cookies. Exports to CSV, JSON, Excel and XML.
Torre's own company API is invite-only and still in private beta, so the practical route to this data is the public search surface, which is what this actor reads. It also handles the part that quietly breaks home-made scripts: Torre ignores filters sent at the top level of a query and applies them only inside an and[] wrapper, so a script that looks like it filters returns the entire unfiltered result set instead. This actor sends the wrapper, and every filter below was measured against Torre's own result counts before it shipped.
| Who uses it | What they scrape Torre for |
|---|---|
| Technical recruiters | Remote engineers by skill, seniority and timezone overlap |
| Sourcing teams | Filling a candidate pipeline with people already open to offers |
| Talent marketplaces | Supply-side mapping of who is available and at what rate |
| Startup founders | Co-founder and early hire search across Latin America |
| Compensation analysts | Real pay expectations by skill, currency and region |
What it does
- 🔍 Searches Torre by skill or role, with minimum experience or self-reported proficiency
- 🌎 Filters by remote availability, timezone range, spoken language and fluency
- 💼 Filters by what the person is open to: full-time, flexible jobs, internships, hiring, mentoring, networking
- 💵 Filters by pay expectation range, in 7 currencies and 3 periods
- 🧬 Optional genome enrichment: full work history, education, detailed skills with proficiency, contact links and languages
- 🎯 Direct mode: pass a list of Torre usernames and skip search entirely
- 🧹 Never emits a null. Withheld values come back as
Not Disclosed, inapplicable ones asN/A, booleans asYesorNo
What you can do with Torre data
Build a sourcing pipeline that is already qualified. Torre profiles state what the person is open to, so filtering on full-time-employment plus a skill and a timezone gives you a shortlist of people who are actually receptive, not a scrape of everyone who once listed Python.
Benchmark compensation honestly. Each profile carries a pay expectation with currency, period and an hourly USD normalisation. Pull a skill across a region and you have a real distribution instead of a survey.
Map remote talent by timezone, not by country. The timezone filter takes a GMT offset range, which is the number that actually decides whether someone overlaps with your team.
Enrich candidates you already have. Direct mode takes a list of usernames and returns full genomes, so an existing shortlist gets work history, education and contact links in one run.
Why choose this scraper
| What you get | |
|---|---|
| Filters that work | Every filter measured against Torre's result totals; the ones Torre silently ignores are not offered |
| Verified dropdowns | Every enum value tested live. 7 plausible-looking values that Torre rejects are excluded |
| No always-null columns | Null audit on every run; fields Torre never returns are dropped, not shipped empty |
| Honest dates | Torre sends months as names, so March 2021 parses to 2021-03 instead of vanishing |
| Pay only for what returns | Enrichment blocks bill only when they actually come back with data |
| One genome fetch | Tick six enrichment blocks and the expensive call still happens once, not six times |
How it compares
There is no other Torre scraper on the Apify Store, so the honest comparison is against the two things people actually do today. Writing your own script is cheap until you hit the and[] wrapper problem, at which point your filters silently stop working and you do not find out until someone questions the results. Requesting Torre's official company API gets you a supported contract, and you should do that if you can, but it is in private beta and gated behind an access request.
| Route | Filters honoured | Setup | Enrichment |
|---|---|---|---|
| This actor | 7, all measured | None | Genome blocks, opt-in |
| Home-made script | Silently 0 unless you find the wrapper | Hours | Build it yourself |
| Torre official API | Full | Access request, private beta | Full |
What a Torre profile looks like
One real row from a verified run, using Torre's own founder as the example so the sample publishes a public figure rather than a private candidate.
{"username": "torrenegra","name": "Alexander Torrenegra","headline": "Founder @ Torre.ai | Sign up for my newsletter at me.torrenegra.com","location": "Napa, California, United States","profileUrl": "https://torre.ai/torrenegra","verified": "Yes","remote": "N/A","openTo": [],"topSkills": "Financial reporting, Analysis, Visionary, Analytics, Salesforce CRM","skillCount": 93,"weight": 24682.9228,"subjectId": "13","compensationAmount": "Not Disclosed","compensationVisibility": "Not Disclosed","country": "United States","timezone": "America/Los_Angeles","profileCompletion": 1,"workHistory": [{"title": "Founder and CEO","organization": "Torre.ai","fromDate": "2021-09","toDate": "Present","isCurrent": "Yes","remote": "Yes","responsibilities": [],"recommendations": 46}],"languages": [{ "language": "English", "code": "en", "fluency": "fully-fluent" },{ "language": "Spanish", "code": "es", "fluency": "fully-fluent" }],"contactLinks": [{ "name": "twitter", "url": "https://twitter.com/torrenegra" },{ "name": "github", "url": "https://github.com/torrenegra" }],"scrapedAt": "2026-09-21T22:31:04.118Z"}
Configure the run
Set a skill or role and a minimum experience level, then add whichever filters matter. Leaving a filter empty skips it. Enrichment blocks are off by default because they add one request per person.
Remote Python engineers in the Americas, open to full-time work:
{"searchTerm": "python","experience": "3-plus-years","remoteOnly": true,"openTo": "full-time-employment","timezoneFrom": "GMT-08:00","timezoneTo": "GMT-03:00","maxItems": 500}
Spanish-speaking designers with pay expectations under 4000 USD per month:
{"searchTerm": "product design","experience": "2-plus-years","languageCode": "es","languageFluency": "fully-fluent","compensationMin": 500,"compensationMax": 4000,"compensationCurrency": "USD$","compensationPeriodicity": "monthly","maxItems": 1000}
Enrich a shortlist you already have:
{"handles": ["torrenegra", "some-other-handle"],"includeGenome": true,"includeExperience": true,"includeContactLinks": true,"maxItems": 100}
Pricing
Pay per event. The base profile row is billed once, and every enrichment block bills only when it returns data.
| Event | Price |
|---|---|
| Actor start | $0.02 |
| Profile scraped | $0.007 |
| Search page (30 profiles) | $0.004 |
| Genome fetched | $0.006 |
| Work history | $0.002 |
| Education | $0.001 |
| Detailed skills | $0.002 |
| Contact links | $0.002 |
| Languages | $0.001 |
| Profiles | Base rows only | With full enrichment |
|---|---|---|
| 100 | $0.74 | $2.14 |
| 1,000 | $7.16 | $21.16 |
| 10,000 | $71.36 | $211.36 |
Free users
Free Apify accounts get 10 rows per run as a preview. Everything else works the same, including filters and enrichment. Upgrade to lift the cap to 1,000,000 rows.
Run it
- Create a free Apify account, which comes with $5 of platform credit.
- Open the actor, enter a skill or role, and pick a minimum experience level.
- Add filters for remote, timezone, language or pay expectation if you need them.
- Click Start, then export the dataset as CSV, JSON, Excel or XML.
Use with AI agents (MCP)
claude mcp add apify --transport sse https://mcp.apify.com/sse?actors=acquistion-automation/torre-scraper
Then ask in plain language:
- "Find me remote Python engineers on Torre with 5+ years who are open to full-time work"
- "Pull Spanish-speaking product designers from Torre and show their pay expectations"
- "Get the full work history for these Torre usernames"
Troubleshooting
No results at all. Torre rejects a skill query without an experience or proficiency level. Leave the Minimum experience dropdown on a value, or pick a proficiency instead.
Fewer rows than I asked for. Free accounts are capped at 10 rows per run. Beyond that, the filter combination may simply match fewer people than your Max Items value; the log prints the true match count before it starts writing.
A filter seems to do nothing. Check the log line that prints the query. If a filter you set is missing from it, you left a dependent field empty: language needs a fluency, timezone needs a start offset, and pay needs a minimum.
An enrichment field is empty. Enrichment needs its checkbox ticked and the genome fetched. If the checkbox is on and the field is still empty, that person did not publish that section; the row shows Not Disclosed rather than a null.
The run is slow. Genome enrichment adds one request per person and Torre answers those in a few seconds each. A 1,000 row run without enrichment finishes in minutes; with enrichment, budget an hour and raise the timeout.
FAQ
| Question | Answer |
|---|---|
| Do I need a Torre account? | No. No login, no API key, no cookies. |
| How many profiles are reachable? | 2,699,211 at the last measurement. |
| Why does Torre need an experience level? | Its API returns HTTP 500 for a skill query without experience or proficiency. |
| Can I filter by country? | Not on people search. Torre accepts a location filter there but ignores it, so it is not offered. Use the timezone range instead. |
| Why are some pay expectations hidden? | Torre lets people keep compensation private; those rows return Not Disclosed. |
| What is the difference between skills and detailed skills? | The search row gives names only. Detailed skills adds proficiency, recommendations and weight, and needs the genome. |
| Can I scrape a specific person? | Yes. Put their username in the Specific Torre usernames field and search is skipped. |
| Does ticking every enrichment block cost six genome fetches? | No. The genome is fetched once per person and reused by every block. |
| What happens if a person deletes their profile mid-run? | That row is skipped and logged. The run continues. |
| Is the data live? | Yes, every run hits Torre directly. Rows carry profileUpdatedAt from Torre and scrapedAt from the run. |
🔗 More from Acquisition Automation Co.
- Clutch Agencies Scraper
- AIA Architect Finder Scraper
- BizBuySell Scraper
- SAM.gov Contract Opportunities Scraper
- IRS Exempt Organizations Scraper
About Acquisition Automation Co.
We build automation for people buying businesses. The repetitive part of an acquisition search, checking listings, pulling public records, tracking owners and assets, is work a machine should do, so the buyer's time goes into judging deals instead of collecting them.
We add new Actors regularly. If there is a source you need and do not see here, tell us.
🆘 Support
Open an issue in the Issues tab of this Actor with your run ID, the input you used, and what you expected to get back.
⚠️ Disclaimer
This is an unofficial scraper, not affiliated with or endorsed by Torre. It collects only data that Torre publishes publicly. Torre profiles describe identifiable people, so the output is personal data: under GDPR, CCPA and PIPL you are the controller of anything you store, and you are responsible for having a lawful basis, for telling people you hold their data, and for honouring deletion requests. Torre's terms of service restrict automated collection, so review them and your own obligations before running this at scale.