# Job Feed Normalizer & Deduplicator (`pietrofilippo/job-feed-normalizer-deduplicator`) Actor

Normalize supplied job records and identify duplicates by source ID or canonical URL, without fuzzy merging.

- **URL**: https://apify.com/pietrofilippo/job-feed-normalizer-deduplicator.md
- **Developed by:** [Pietro Filippo](https://apify.com/pietrofilippo) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 processed records

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Job Feed Normalizer & Deduplicator

Turn supplied job records into a consistent schema and identify exact duplicates. No source websites or AI services are called.

```json
{
  "records": [
    {"feed":"acme","id":"123","name":"Engineer"},
    {"feed":"acme","id":"123","name":"Engineer"}
  ],
  "mapping": {"source":"feed","jobId":"id","title":"name"}
}
```

Mapping keys: `recordId`, `source`, `jobId`, `url`, `title`, `company`, `location`. Unmapped fields use the same input name. Dot paths such as `job.title` are supported. A source namespace must identify the company/feed whose IDs are unique; two unrelated sources may reuse the same numeric ID.

Each input row produces a row with `inputIndex`, the normalized fields and `disposition`: `unique`, `duplicate` or `invalid`. Duplicate rows include `duplicateOfInputIndex`; invalid rows include a reason. Keep only `unique` rows for your cleaned feed. The duplicate report remains available in the same dataset. `SUMMARY` contains counts.

Identity precedence: recognized Greenhouse/Lever URL identity; otherwise the exact supplied source plus job ID; otherwise canonical URL. Known tracking parameters and URL fragments are removed, but unknown query parameters are preserved. Rows are not merged by similar titles or company names. When an explicit generic source/ID exists it takes precedence over its URL; mixing ID-based and URL-only rows can leave duplicates, deliberately favoring separate records over false merges.

Maximum 10,000 input rows. A valid row requires a URL or source plus job ID; title alone is insufficient. Only mapped scalar fields are exported; input objects are not copied wholesale. Configured price: $0.50 per 1,000 valid processed input rows via `record-processed`, including duplicates, plus Apify's $0.00005 start event (one event at the default 256 MB memory). Invalid rows have no processing charge; the start fee still applies. Check the current Pricing tab.

# Actor input Schema

## `records` (type: `array`):

1–10,000 JSON objects. Each valid row needs a URL or both a source namespace and jobId.

## `mapping` (type: `object`):

Optional output-field to input-field mappings. Dot paths are supported. Fields: recordId, source, jobId, url, title, company, location.

## Actor input object example

```json
{
  "records": [
    {
      "source": "example-company",
      "jobId": "1",
      "title": "Engineer",
      "url": "https://example.com/jobs/1"
    },
    {
      "source": "example-company",
      "jobId": "1",
      "title": "Engineer",
      "url": "https://example.com/jobs/1?utm_source=feed"
    }
  ],
  "mapping": {
    "jobId": "jobId",
    "title": "title",
    "url": "url"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (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 = {
    "records": [
        {
            "source": "example-company",
            "jobId": "1",
            "title": "Engineer",
            "url": "https://example.com/jobs/1"
        },
        {
            "source": "example-company",
            "jobId": "1",
            "title": "Engineer",
            "url": "https://example.com/jobs/1?utm_source=feed"
        }
    ],
    "mapping": {
        "jobId": "jobId",
        "title": "title",
        "url": "url"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("pietrofilippo/job-feed-normalizer-deduplicator").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 = {
    "records": [
        {
            "source": "example-company",
            "jobId": "1",
            "title": "Engineer",
            "url": "https://example.com/jobs/1",
        },
        {
            "source": "example-company",
            "jobId": "1",
            "title": "Engineer",
            "url": "https://example.com/jobs/1?utm_source=feed",
        },
    ],
    "mapping": {
        "jobId": "jobId",
        "title": "title",
        "url": "url",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("pietrofilippo/job-feed-normalizer-deduplicator").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 '{
  "records": [
    {
      "source": "example-company",
      "jobId": "1",
      "title": "Engineer",
      "url": "https://example.com/jobs/1"
    },
    {
      "source": "example-company",
      "jobId": "1",
      "title": "Engineer",
      "url": "https://example.com/jobs/1?utm_source=feed"
    }
  ],
  "mapping": {
    "jobId": "jobId",
    "title": "title",
    "url": "url"
  }
}' |
apify call pietrofilippo/job-feed-normalizer-deduplicator --silent --output-dataset

```

## MCP server setup

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

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/282ajDRl2Gjavuqet/builds/4iQ1n0kKPzn2v8Irj/openapi.json