weworkremotely-jobs

The newest jobs in one We Work Remotely category feed: job title, company, the job's page, region, the feed's category, the job type (Full-Time or Contract; the programming feed carries none), publication time and the first 300 characters of the description. category picks the feed: programming, design, devops, support, sales, product, management, other or all (other sits behind a Cloudflare challenge today: no rows, no charge). keyword keeps jobs whose title or company mentions it. limit caps the rows (up to 100). One fetch per run.

stagedweworkremotely.comWASM module8 fields2 unitsfresh 15 min
‹ Recipes
…json
POST api.crawl4ai.com/recipes/…

$ crawl recipe

              
Live · your key · counts against your quota✓ 200 OK
# Hit Run - the rows render here as a table, with the cost

Fields

8 columns on every row. null means the site does not state it.
fieldtypemeaning
titlestring
companystring
urlstring
regionstring
categorystring
type
publishedstring
descriptionstring

null means the site does not state it.

titlestring
companystring
urlstring
regionstring
categorystring
type
publishedstring
descriptionstring

How it behaves

Cost. 2 units. A failed run costs 0.

Freshness 15 min. The same input within 15 min is served from cache at 0 units.

Questions about this recipeQuestions

Short answers. The API reference has the long ones.

Call POST /recipes/weworkremotely-jobs with your key and category and keyword and limit. You get rows with the 8 fields above. The recipe is tested against the live site every 6 hours.

Need more from We Work Remotely?

Extra fields, higher volume, or a private copy with a freshness SLA. We build it on Enterprise.

Request a change

For developers

Get a free API key and run your first crawl.

1,000 credits every month. No credit card. Your self-hosted setup keeps working.

For teams

Talk to us about volume, regions and an SLA.

A 30-minute call with the team that writes the crawler. DPA on request, invoice billing, your choice of US, EU or Singapore.