# Home Depot Jobs API (`apifmcpfactory/homedepot-jobs-api`) Actor

Every open role at The Home Depot as structured JSON or CSV, at $1.50 per 1,000 jobs. No setup — press Start. Title, location, country, employment type, remote type, posted date and apply link, with change detection between runs and a white-label hiring report.

- **URL**: https://apify.com/apifmcpfactory/homedepot-jobs-api.md
- **Developed by:** [Howth Technology Factory](https://apify.com/apifmcpfactory) (community)
- **Categories:** Jobs, Developer tools, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Home Depot Jobs API

Every open role at The Home Depot, as clean structured data. **No setup — press Start.**

> Unofficial. Not affiliated with, endorsed by, or sponsored by The Home Depot. Job data is read from The Home Depot's own public careers feed.

***

### What it does

Reads The Home Depot's own public careers feed and returns one row per open role: title, location, country, employment type, remote type, the posted date and the apply link. It de-duplicates, flags likely reposts without deleting them, tells you what changed since your last run, and can produce a white-label hiring report in HTML and PDF.

Our platform-wide listings ask you for a careers URL or a board token — and for this platform, also a datacentre and a site name that cannot be derived from a company name. **This listing asks for none of it.** The Home Depot's board is already configured. Press Start.

### Who it's for

- **Recruiters and sourcers** tracking The Home Depot for new openings.
- **Market and talent researchers** measuring where The Home Depot is hiring, by location and country.
- **AI agents** that need The Home Depot's live roles as structured JSON — see the MCP block below.

### What a default run costs, and how to change it

The Home Depot had **1,009 roles open** when this listing was built. At $0.0015 per role, returning all of them would bill you $1.51 — so a default run does **not** do that.

**The default is the newest 100 roles, which costs about $0.15.** Raise `maxJobs` when you want more, or set it to `0` for no cap at all. When a run is capped, the result says so rather than quietly handing you a short list.

Filtering costs less than not filtering: you are charged for what comes back, so a title or location filter in the input is cheaper than trimming afterwards.

### Sample output

From a real run on 2026-08-02 — **100 roles in 43 seconds**, no retries and no errors.

```json
{
  "source": "workday",
  "company": "The Home Depot",
  "title": "Corporate Security Officer (1st Shift)",
  "location": "STORE SUPPORT CENTER, ATLANTA - 9090",
  "country": "US",
  "workplaceType": "onsite",
  "employmentType": "full-time",
  "postedAt": "2026-08-02",
  "isRemote": false,
  "description": null
}
```

#### What this feed actually publishes

Measured on those same 100 roles. A field the platform does not publish is `null` — never guessed, never inferred from the job title.

| Field | Coverage | |
|---|---|---|
| `title`, `postedAt`, `applyUrl` | 100 / 100 | always present |
| `location` | 99 / 100 |  |
| `country` | 100 / 100 |  |
| `employmentType` | 98 / 100 |  |
| `workplaceType` | 56 / 100 | only where the employer sets it |
| `department`, `team`, `seniority`, `salary` | 0 / 100 | not published by this platform |

That run also flagged **4 repost groups** — same role, same place, more than one posting. They are reported, never merged: a wrongly collapsed repost hides a real vacancy.

### The rules this product is built on

1. **Job descriptions belong to the employer.** `includeDescription` is **off by default**. A job advert is The Home Depot's copyrighted text; the structured fields are not.
2. **No personal data, ever.** No recruiter names, no hiring-manager contacts, no emails, no phone numbers. There is nowhere in the schema to put one, and a test fails the build if a personal-data field appears.
3. **Unofficial, reading a public feed.** No key, no login, no browser automation, no anti-bot circumvention. Unofficial. Not affiliated with, endorsed by, or sponsored by The Home Depot. Job data is read from The Home Depot's own public careers feed.

### Monitoring

Set `onlyNewSinceLastRun` and schedule it. The first run stores a baseline and returns everything — nothing is reported as a change, because everything being new the first time is not news. After that you get only what appeared since, and the summary still tells you what was removed and what was edited. Add a `webhookUrl` for a JSON summary when anything moves.

### FAQ

**Do I need to configure anything?** No. Press Start.

**Why only 100 roles by default?** Cost control — see above. One number raises it.

**Why is `salary` empty?** Because this platform's public feed does not carry it. Left null rather than guessed.

**Why is `department` empty?** Same reason.

**Is a role listed here definitely still open?** It is listed because The Home Depot published it and has not taken it down. Postings are returned as published, not as verified.

**Can I get the full job description?** Yes — set `includeDescription: true`. See rule 1 for why it is off by default.

**Can I point this at a different employer?** Yes — the board field stays editable, and any board on the same platform works. For arbitrary employers, use the platform-wide listing instead.

### MCP — for AI agents

```json
{ "mcpServers": { "jobs": { "url": "https://jobs-api.mcpize.run" } } }
```

`search_jobs` $0.01 · `get_company_jobs` $0.01 · `monitor_jobs` $0.02 · `generate_report` $0.10

***

*Unofficial. Not affiliated with, endorsed by, or sponsored by The Home Depot. Job data is read from The Home Depot's own public careers feed. Job adverts are the property of the employers who published them.*

# Actor input Schema

## `companies` (type: `array`):

Already set to The Home Depot's own careers board. You do not need to change this — press Start. It stays editable only so the same run can be pointed at another board on the same platform.

## `dataPreset` (type: `string`):

All jobs is right for most uses. New only is for scheduled runs. With descriptions returns the advert body as well — see the note below before switching it on.

## `includeDescription` (type: `boolean`):

Off by default, and deliberately. A job advert is the employer's copyrighted text; the structured fields are not. Leaving it off means smaller payloads, faster runs and a cleaner licence position. Switch it on when your use needs the body text.

## `onlyNewSinceLastRun` (type: `boolean`):

For scheduled runs. The first run on a board always returns everything and stores the baseline; after that you get only what appeared since. Removed and edited postings are still reported in the summary and the report.

## `titleIncludes` (type: `array`):

For example engineer, designer, product. Leave empty for every role.

## `titleExcludes` (type: `array`):

For example intern, contract. Applied after the include list.

## `locationIncludes` (type: `array`):

For example Dublin, Germany, Remote.

## `departmentIncludes` (type: `array`):

Only useful where The Home Depot publishes one — see the platform notes in the README.

## `employmentTypes` (type: `array`):

Normalised across every platform in this family. A platform that does not publish one leaves it empty, and those jobs are excluded when you set a filter here.

## `remoteOnly` (type: `boolean`):

Uses the platform's own remote flag where there is one, and the location text where there is not.

## `postedWithinDays` (type: `integer`):

Leave empty for all. Jobs with no published date are kept rather than silently dropped.

## `maxJobs` (type: `integer`):

This is the cost control, and it is set deliberately low. The Home Depot can have thousands of roles open, and at $0.0015 per role an uncapped run adds up fast — so a default run returns the newest 100 and costs about 0.15. Raise it when you want more, or set 0 for no cap at all.

## `maxJobsPerCompany` (type: `integer`):

Caps what each board can return, and therefore what it can cost. Leave empty for all of them.

## `sortBy` (type: `string`):

Undated postings always sort last rather than pretending to be the oldest.

## `generateReport` (type: `boolean`):

A client-ready review of the whole run: where the hiring is by department and location, what changed since the last run, and every open role in one table. Costs nothing extra.

## `reportFormat` (type: `string`):

HTML opens in any browser and prints cleanly to A4. PDF is ready to send to a client.

## `reportCompanyName` (type: `string`):

Appears on the report. Setting this (or a logo) puts it in white-label mode and takes our name off.

## `reportLogoUrl` (type: `string`):

A direct link to a PNG, JPG or SVG.

## `reportAccentColor` (type: `string`):

Hex colour used for headings, for example #1E3A8A.

## `reportFooterText` (type: `string`):

Appears at the bottom of every page — usually your company name or a client reference.

## `exportFormat` (type: `string`):

The dataset is always JSON. This additionally writes flat comma-separated files you can open in a spreadsheet — the jobs, the boards, and what changed.

## `webhookUrl` (type: `string`):

Called with a JSON summary when a board gains, loses or changes a posting. Nothing fires on the first run, because everything is new the first time and that is not news.

## `userAgent` (type: `string`):

Every request declares who is making it and how to reach them. The default identifies this actor. If you are running at volume, put your own company name and email here.

## `requestsPerSecond` (type: `integer`):

Shared across the whole run. The default is deliberately gentle: these are free public feeds and staying welcome on them matters more than finishing half a second sooner.

## Actor input object example

```json
{
  "companies": [
    "https://homedepot.wd5.myworkdayjobs.com/CareerDepot"
  ],
  "dataPreset": "all-jobs",
  "includeDescription": false,
  "onlyNewSinceLastRun": false,
  "remoteOnly": false,
  "maxJobs": 100,
  "sortBy": "newest",
  "generateReport": false,
  "reportFormat": "both",
  "reportAccentColor": "#1E3A8A",
  "exportFormat": "none",
  "userAgent": "Howth Technology Factory jobs-api apifymcpfactory@gmail.com",
  "requestsPerSecond": 4
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `report` (type: `string`):

No description

## `reportPdf` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `csv` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "https://homedepot.wd5.myworkdayjobs.com/CareerDepot"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apifmcpfactory/homedepot-jobs-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "companies": ["https://homedepot.wd5.myworkdayjobs.com/CareerDepot"] }

# Run the Actor and wait for it to finish
run = client.actor("apifmcpfactory/homedepot-jobs-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    "https://homedepot.wd5.myworkdayjobs.com/CareerDepot"
  ]
}' |
apify call apifmcpfactory/homedepot-jobs-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=apifmcpfactory/homedepot-jobs-api",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/rVsEScBJY7Zs9kmef/builds/jfUwqUBKD2YpdMAEq/openapi.json