The Muse Jobs Scraper

The Muse Jobs Scraper exports public job listings from The Muse with titles, employers, locations, seniority levels, publication dates, application links and job descriptions. Use the results for recruiting research, job aggregation and hiring analysis, then download JSON, CSV or Excel.

Search by company, location and category using the public search pages, with complete descriptions from each job's structured data. Keyword and date filters narrow the returned jobs, so a small page limit can produce fewer matches than your requested maximum.

The Muse has replaced its former public API. Current jobs use string UUID identifiers (older exports used numbers). Company IDs and some category, seniority and tag metadata are no longer supplied; missing values remain null or empty arrays. A levels filter only matches explicitly published labels and can return no results when labels are absent; no seniority is guessed from a title.

Quick start

1. Enter your filters in Apify. Use The Muse's location, category and level names.
2. Start with a small result and page limit, like this input:

{
  "keywords": [
    "engineer"
  ],
  "locations": [
    "Remote"
  ],
  "categories": [
    "Software Engineering"
  ],
  "maxItems": 20,
  "pageLimit": 3
}

3. Click Start, then open the dataset to review and export the matching jobs. No The Muse login or cookies are required.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a preconfigured search to get started:

• The Muse Remote Software Engineering Jobs — Find engineering roles with location and category filters.
• The Muse Target Company Jobs — Collect listings for selected employers.
• The Muse Python Job Description Search — Look for Python mentions across job titles and descriptions.

What you get

• One record per matching job, with employer identifiers and public application links.
• Job descriptions in text and HTML when supplied by The Muse.
• Locations, categories, levels and tags as arrays when explicitly supplied; missing lists stay empty.
• Publication and collection timestamps for your own reporting and comparisons.

Who is it for?

• Recruiters and career researchers building targeted lists of public roles.
• Job aggregators collecting descriptions and application links.
• Hiring analysts and sales teams researching which employers are recruiting.

The scraper collects listings. Historical comparisons, alerts and analysis belong in your downstream workflow.

Input settings

Setting	JSON key	What it does
Keywords	keywords	Match any supplied term across title, employer, locations, categories, levels and description. Optional.
Locations	locations	Source location names, such as Remote or New York, NY. Optional.
Companies	companies	Employer names. Omit to search across employers.
Job categories	categories	Source categories, such as Software Engineering. Optional.
Seniority levels	levels	Exact explicitly published labels only. Often absent on the current site; unlabeled jobs are skipped. Leave empty for complete coverage.
Maximum jobs	maxItems	Maximum saved matches. Default 50, form example 20, range 1–10,000.
Maximum pages	pageLimit	Maximum total pages scanned across location/company/category combinations. Default 5, form example 3, range 1–500.
Start page	pageStart	First result page to scan. Default 1.
Published after date	dateFrom	Inclusive minimum publication date in ISO format. Optional.
Proxy configuration	proxyConfiguration	Existing advanced managed or custom proxy settings. Managed proxy is used when omitted.
Maximum run time	maxRunSeconds	Safety budget from 35–270 seconds. Default 270.

The form prefills engineer, Remote and Software Engineering. These are examples, not API defaults. Omitted filter arrays do not add those filters.

Use the proxy editor for existing managed settings or your own proxy URLs. An explicit {"useApifyProxy": false} without custom URLs uses direct requests. Custom proxy settings remain supported. Direct access depends on the source accepting requests from your environment.

Keyword matching is case-insensitive and accepts a match on any supplied keyword. The date filter skips jobs without a publication date. Results retain the source order. There is no sorting control or individual job-URL input.

Output data

Each saved row represents a matching job. Missing source values can be null, while missing list fields become empty arrays.

Field	Meaning
id, title	The Muse job UUID (string; legacy numeric IDs also supported) and title.
companyName, companyId, companyShortName	Employer name, identifier and slug when available.
locations, categories, levels, tags	Lists of location, category, seniority and tag names.
publicationDate	Source publication timestamp, or null.
type, shortName, modelType	Source job type, job slug and model label.
descriptionHtml, descriptionText	Source description and its plain-text representation.
applyUrl, jobUrl	The same source landing-page URL, or null.
sourcePage, scrapedAt	Source page number and collection timestamp.

This synthetic example shows the output shape, not an observed job:

{
  "id": 123,
  "title": "Example engineering role",
  "companyName": "Example employer",
  "companyId": 456,
  "companyShortName": "example-employer",
  "locations": ["Remote"],
  "categories": ["Software Engineering"],
  "levels": ["Mid Level"],
  "tags": [],
  "publicationDate": null,
  "type": null,
  "shortName": null,
  "modelType": "jobs",
  "descriptionHtml": null,
  "descriptionText": null,
  "applyUrl": null,
  "jobUrl": null,
  "sourcePage": 1,
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged once when the run begins, including when no jobs match.

The item event is charged for each matching job saved to the dataset. Filtered-out jobs do not produce saved-item charges. The Actor does not write paid error or status rows. Apify platform usage can also apply under the current pricing terms.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with a small search. Check that the source labels match the roles you want before increasing limits.
• Broaden one filter at a time. Exact source wording matters for companies, categories and locations.
• Allow enough pages for narrow keywords. Keyword and date matching happen after jobs are retrieved.
• Choose the right description field. Use descriptionText for analysis and descriptionHtml when formatting matters.

Limits and caveats

Only public listings returned by The Muse are available. This is not an official The Muse product and does not retrieve applicant data or private employer information.

A run stops at its job limit, page limit, end of available results or safety budget. The safety budget reserves time to finish, so it may stop collecting before the full number of seconds has elapsed. Completed jobs are preserved.

A successful run can contain zero jobs when no returned listings match. RUN_SUMMARY records counts, unavailable job pages, missing seniority labels and any customer cost/deadline stop. Customer limits preserve completed rows and succeed with a warning. Source access, malformed data, storage or billing errors still fail a run. A full result count and unchanged ordering across separate runs are not guaranteed because listings change.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~the-muse-jobs-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["engineer"],"maxItems":20,"pageLimit":3}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/the-muse-jobs-scraper').call({
  keywords: ['engineer'], maxItems: 20, pageLimit: 3
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/the-muse-jobs-scraper").call(run_input={
    "keywords": ["engineer"], "maxItems": 20, "pageLimit": 3
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with The Muse Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's The Muse Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/the-muse-jobs-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use The Muse Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/the-muse-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Find up to 20 remote software engineering jobs on The Muse and put the employer names and application links in a table.”
• “Collect up to 30 current The Muse listings for Atlassian and summarize the responsibilities from their descriptions.”
• “Get up to 20 senior data and analytics jobs from The Muse and group the returned roles by employer.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I collect remote jobs or a specific company's roles?

Yes. Use locations with source labels such as Remote or Flexible / Remote, or provide employer names in companies. Available results depend on current listings and the source's labels.

Can I search job descriptions for a skill?

Yes. keywords checks job descriptions as well as titles, employer names and other listing text. It matches any supplied term, not an exact multi-keyword conjunction.

Is this a The Muse jobs API alternative?

You can call this Actor through Apify's API or hosted MCP service and retrieve structured job records. It is not an official The Muse API service and needs no The Muse login. Apify API calls require Apify authentication.

Can I export the jobs or compare repeated searches?

Download the dataset as JSON, CSV or Excel, or read it through the API. You can save an input as a task. Comparing runs or sending alerts requires your own workflow.

Why did I get fewer jobs than requested?

maxItems is a ceiling, not a promised count. Relax a filter, check the source's category and location names, or allow more pages. Keyword and date filtering can leave a successful dataset empty.

What is charged if there are no matches?

The start event still applies, but there are no saved-job item events. See the live Pricing tab for current terms.

Related Actors

• Ashby Jobs Scraper — Collect roles from Ashby job boards.
• ATS Jobs Scraper for 6 ATS Sources — Work across supported applicant-tracking job sources.
• Built In Jobs Scraper — Research jobs on Built In.
• Greenhouse Jobs Scraper — Collect public Greenhouse roles.
• Remote.com Jobs Scraper — Explore another remote-jobs source.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥