# Built In Job Details, Full Text and Benefits (`gubidonius/builtin-job-details`) Actor

The full advert from builtin.com: employer text as plain text, pay range and period, posting and expiry dates, every location, employment type, the board's skills list and the employer's full benefits list. By advert URL or from a search.

- **URL**: https://apify.com/gubidonius/builtin-job-details.md
- **Developed by:** [Gregory Bolshakov](https://apify.com/gubidonius) (community)
- **Categories:** Jobs, Lead generation, Business
- **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/actors/running/actors-in-store.md#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

## Built In Job Details, Full Text and Benefits

The advert page from builtin.com, one row per advert: the employer's full text as plain
text, the pay range with its period, the posting and expiry dates, every location, the
employment type, the board's Skills Required list and the employer's whole benefits list.
Give it advert URLs, or a search and it reads the first adverts the board returns. No key
and no login.

### Why the URL and not the id

The board opens an advert only at its own address, `/job/<slug>/<id>`. The same id under
any other slug answers not found, measured on 11 September 2026. So a bare id cannot be
turned into a page, and one given here is reported in `RUN_SUMMARY` rather than guessed
at. The `url` column of builtin-jobs is what goes in.

### What the page adds to the search card

The card shows a summary the board generates. The page carries the employer's text, kept
here with its paragraphs and list items, and `descriptionChars` says how long it is. The
page also carries the board's structured data, which is where `datePosted`,
`validThrough`, `employmentType` and the pay figures come from when the label alone would
be ambiguous. `salarySource` says which one answered.

`benefits` is the employer's list, not the advert's: every advert of one employer carries
the same list, and it is the same list builtin-company-details reads grouped under its
headings.

### What is not here

The card's skill tags are on the search result, so they are in builtin-jobs. The
"Skills Required" list here is a different thing, written by the board from the text,
and it is named that way so the two are never mistaken for each other.

### Billing

Two events: a start fee charged only once a row is returned, and a per-row fee charged
after each row is written. A URL that answers not found costs nothing.

# Actor input Schema

## `jobUrls` (type: `array`):

Advert pages to read, as their URL on the board, for example https://builtin.com/job/staff-engineer-ce-cad/10459665. The url column of builtin-jobs is what goes here. The board opens an advert only at its own slug, so a bare id cannot be resolved and is reported rather than guessed.

## `search` (type: `string`):

Instead of URLs, or as well as them: search the board and read the first adverts found, in the board's own order. For a big search run builtin-jobs first and pass its URLs.

## `categories` (type: `array`):

One of the board's 16 categories for the search, by name or alias. The board filters on one at a time.

## `workplaceTypes` (type: `array`):

Remote, Hybrid, In-Office, for the search.

## `experienceLevels` (type: `array`):

Internship, Entry level, Junior, Mid level, Senior, Expert/Leader, Not specified, for the search.

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

Only adverts posted in the last 1, 3, 7 or 30 days. 0 means no date filter.

## `allLocations` (type: `boolean`):

Search every country the board lists rather than the United States only.

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

Most adverts to read, URLs and search together, and the most you will be charged for.

## Actor input object example

```json
{
  "jobUrls": [],
  "search": "data engineer",
  "categories": [],
  "workplaceTypes": [],
  "experienceLevels": [],
  "postedWithinDays": 0,
  "allLocations": false,
  "maxJobs": 25
}
```

# Actor output Schema

## `results` (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 = {
    "jobUrls": [],
    "search": "data engineer",
    "categories": [],
    "workplaceTypes": [],
    "experienceLevels": [],
    "postedWithinDays": 0,
    "allLocations": false,
    "maxJobs": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("gubidonius/builtin-job-details").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 = {
    "jobUrls": [],
    "search": "data engineer",
    "categories": [],
    "workplaceTypes": [],
    "experienceLevels": [],
    "postedWithinDays": 0,
    "allLocations": False,
    "maxJobs": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("gubidonius/builtin-job-details").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "jobUrls": [],
  "search": "data engineer",
  "categories": [],
  "workplaceTypes": [],
  "experienceLevels": [],
  "postedWithinDays": 0,
  "allLocations": false,
  "maxJobs": 25
}' |
apify call gubidonius/builtin-job-details --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gubidonius/builtin-job-details"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/36rgx8oRBogJFSFqt/builds/PbccOsHte4gHadOCa/openapi.json