Workana has no public API for project listings, and unusually it also closes the obvious workaround: its robots.txt disallows the internal one. That combination shapes what a compliant integration can be.
The short answer
No public listing API, no key, no documented field contract. Anything that reads Workana project data reads the same public pages a visitor's browser receives.
What robots.txt closes off
User-agent: *
Disallow: /api/
Disallow: /*?*ag=1
Disallow: /users/landing_choose*
Disallow: */login*?*
Disallow: */signup*?*
Sitemap: https://www.workana.com/sitemap_index.xmlThe first line is the interesting one. Many sites leave their internal API undisclosed and undefended, and a scraper author who finds it faces a judgement call. Workana removes the judgement call: /api/ is disallowed, so a compliant crawler reads the listing pages.
Note what is not capped here: pagination. Unlike coches.net, which disallows pg=7 and beyond, and Zonaprop, which allows only pages 2 to 5, Workana's robots.txt says nothing about depth. The page-50 limit is the site's own behaviour rather than a stated rule — a distinction worth keeping straight, because one is a declaration and the other is an observation.
The cost of no contract
With no documentation, a parameter that returns HTTP 200 has told you nothing. That is how thirteen of Workana's URL parameters turned out to be decorative: the only way to know was to compare result sets with and without each one — which is what was done.
It is also why the Actor validates a skill slug before running. An undocumented API returns an error for a bad value; Workana returns an empty result set and a 200.
What that means for your pipeline
- Assert on your fields. No versioning means no notice.
- Do your filtering downstream for anything the site does not actually filter, and expect to pay for the rows you discard.
- Do not trust the result counter. It caps at 10,000, so it is not a size for large queries.
- Keep the raw strings. `budget_raw` and `total_bids_raw` exist so a parse can be audited when the rendering changes.
Alternatives
There is no licensed feed of LATAM freelance demand that this project is aware of. The adjacent sources are the other marketplaces, each with its own public surface and its own quirks, and aggregate labour statistics — which describe employment rather than freelance demand and cannot answer “what are clients paying for React work in Argentina this month”.
For that question the public listings are the source, and the Actor documentation states what it yields and where it stops.
