# 17TRACK Package Tracking Scraper | 3,000+ Carriers, Bulk (`trev0n/17track-scraper`) Actor

Track parcels from 3,000+ carriers via 17TRACK in bulk: status, carrier, origin and destination, latest event, ETA, delivery date and the full checkpoint history. Thousands of numbers per run, change monitoring and webhooks.

- **URL**: https://apify.com/trev0n/17track-scraper.md
- **Developed by:** [Paweł](https://apify.com/trev0n) (community)
- **Categories:** E-commerce, Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $12.00 / 1,000 package trackeds

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

## 📦 17TRACK Package Tracking Scraper

🎯 **Track hundreds or thousands of parcels from 3,000+ carriers in one run and get every status, checkpoint and delivery date in a clean table.**

Paste your tracking numbers and get, for each parcel: the current status, the carriers handling it (origin and last-mile), origin and destination country, the latest event, estimated delivery window, delivery date, days in transit and the full checkpoint history. Postal services, express couriers and Chinese e-commerce lines are all covered, and the carrier is detected automatically.

### 🚀 What Does It Do?

This tool automatically looks up your parcels on 17TRACK, the world's largest package tracking platform, and returns **structured, ready-to-use tracking data**. No copying numbers into a website one by one, no 40-numbers-at-a-time limit: add your whole list and hit Start.

💡 **Two ways to use it:**

1. **🔍 One-off tracking** — check the status of a list of parcels right now and export it.
2. **🔔 Monitoring** — schedule it every few hours and get only the parcels with news: a new status, a new checkpoint, a delivery or a problem.

### 👥 Who Is This For?

| 🏢 Use Case                        | 💬 How It Helps                                                                                 |
| ---------------------------------- | ----------------------------------------------------------------------------------------------- |
| 🛒 **Online shops & dropshippers** | See every order's delivery status in one sheet and spot stuck parcels before customers complain |
| 📞 **Customer support teams**      | Answer "where is my order?" instantly with the latest checkpoint and ETA                        |
| 🚚 **Logistics & fulfilment**      | Measure carrier speed and failed deliveries across thousands of shipments                       |
| 🏪 **Marketplace sellers**         | Prove delivery dates for disputes and refund claims on Amazon, eBay, AliExpress                 |
| 🤖 **Automation builders**         | Feed parcel updates into Zapier, Make, n8n, your shop or CRM with the webhook                   |

### ✨ Features

- 🌍 **3,000+ carriers** — postal services worldwide, DHL, UPS, FedEx, DPD, GLS, Cainiao, YunExpress, 4PX and many more
- 🧭 **Automatic carrier detection** — no need to know who ships the parcel
- 🔁 **Origin and last-mile carrier** — both carriers of cross-border parcels, with their own checkpoints
- 🗓️ **Full checkpoint history** — every event with time, location, description and carrier
- 📍 **Status and detail** — In transit, Out for delivery, Delivered, Available for pickup, Exception, Expired and more
- ⏱️ **Delivery metrics** — shipped and delivered dates, days in transit, days since last update, estimated delivery window
- 📦 **Package details** — service type, weight, pieces, reference and local numbers when the carrier shares them
- 🔔 **Change monitoring** — only parcels with news on scheduled runs, with the previous status for each change
- 🪝 **Webhook** — push new and changed parcels to your own systems automatically
- ⚡ **Fast & Scalable** — thousands of numbers per run in batches of 40
- 🧽 **Deduplication** — the same number written differently is tracked once
- 📤 **Export Anywhere** — Download results as JSON, CSV, Excel, or push to Google Sheets, Zapier, Make, or your CRM

### 🎛️ Filters & Options

| Option                                  | What It Does                                               |
| --------------------------------------- | ---------------------------------------------------------- |
| 🏷️ **Tracking numbers**                 | Your parcel numbers, one per line (17TRACK links work too) |
| 🗓️ **Full checkpoint history**          | Include every tracking event, or only the current status   |
| ✅ **Only packages with tracking data** | Leave out numbers that have no information yet             |
| 🧽 **Drop empty fields**                | Leaner rows without empty values                           |
| 🔔 **Monitor changes**                  | Return only parcels with a new status or checkpoint        |
| 🏷️ **Monitoring list name**             | Keep separate histories for separate schedules             |
| 🔁 **Also return unchanged packages**   | Return every parcel in monitoring mode                     |
| 🪝 **Webhook for changes**              | Receive new and changed parcels at your own URL            |
| 🚦 **Parallel browsers**                | Track more batches at the same time                        |
| 🔗 **17TRACK links**                    | Alternative list input for integrations                    |
| 🛡️ **Proxy**                            | Built-in proxy for reliable tracking of large lists        |

### 📦 What You Get (Output Fields)

Every tracking number includes:

#### 📍 Status

| Field          | Example                                                                                                                                          |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| trackingNumber | `CQ123456789DE`                                                                                                                                  |
| found          | `true`                                                                                                                                           |
| status         | `Delivered`                                                                                                                                      |
| subStatus      | `Delivered_Other`                                                                                                                                |
| lastUpdate     | `2026-10-14T19:42:00+02:00`                                                                                                                      |
| latestEvent    | `{"time": "2026-10-14T19:42:00+02:00", "description": "The shipment has been successfully delivered", "location": "PL", "carrier": "DHL Paket"}` |

#### 🚚 Carriers & Route

| Field              | Example                                                              |
| ------------------ | -------------------------------------------------------------------- |
| carrier            | `DHL Paket`                                                          |
| carrierWebsite     | `https://www.dhl.de/en/privatkunden/pakete-empfangen/verfolgen.html` |
| lastMileCarrier    | `Poland Post`                                                        |
| originCountry      | `DE`                                                                 |
| destinationCountry | `PL`                                                                 |
| destination        | `{"country": "PL", "state": null, "city": null, "postalCode": null}` |

#### ⏱️ Timing

| Field                 | Example                     |
| --------------------- | --------------------------- |
| labelCreatedAt        | `2026-10-10T18:03:00+02:00` |
| deliveredAt           | `2026-10-14T19:42:00+02:00` |
| daysInTransit         | `3`                         |
| daysSinceLastUpdate   | `0`                         |
| estimatedDeliveryFrom | `2026-10-13T00:00:00Z`      |
| estimatedDeliveryTo   | `2026-10-15T00:00:00Z`      |

#### 🗓️ History & Details

| Field       | Example                                                                                                                                                      |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| events      | `[{"time": "2026-10-14T08:48:00+02:00", "description": "The shipment has been loaded onto the delivery vehicle", "location": "PL", "carrier": "DHL Paket"}]` |
| eventCount  | `10`                                                                                                                                                         |
| milestones  | `[{"stage": "PickedUp", "time": "..."}, {"stage": "Delivered", "time": "..."}]`                                                                              |
| serviceType | `Shipment for Export`                                                                                                                                        |
| weightKg    | `0.75`                                                                                                                                                       |
| trackingUrl | `https://t.17track.net/en#nums=CQ123456789DE`                                                                                                                |

#### 🔔 Monitoring

| Field          | Example                    |
| -------------- | -------------------------- |
| changeType     | `UPDATED`                  |
| previousStatus | `InTransit`                |
| statusChanged  | `true`                     |
| firstSeenAt    | `2026-11-05T08:00:00.000Z` |

### 📊 Example Output

```json
{
    "trackingNumber": "CQ123456789DE",
    "found": true,
    "status": "Delivered",
    "subStatus": "Delivered_Other",
    "statusDescription": null,
    "carrier": "DHL Paket",
    "carrierKey": 7041,
    "carrierCountry": "DE",
    "carrierWebsite": "https://www.dhl.de/en/privatkunden/pakete-empfangen/verfolgen.html",
    "carrierPhone": "+49 228 4333112 ",
    "lastMileCarrier": "Poland Post",
    "lastMileCarrierKey": 16081,
    "lastMileCarrierWebsite": "http://www.poczta-polska.pl/",
    "lastMileCarrierPhone": null,
    "originCountry": "DE",
    "destinationCountry": "PL",
    "origin": {
        "country": "DE",
        "state": null,
        "city": null,
        "postalCode": null
    },
    "destination": {
        "country": "PL",
        "state": null,
        "city": null,
        "postalCode": null
    },
    "latestEvent": {
        "time": "2026-10-14T19:42:00+02:00",
        "timeUtc": "2026-10-14T17:42:00Z",
        "description": "The shipment has been successfully delivered",
        "descriptionTranslated": null,
        "location": "PL",
        "stage": "Delivered",
        "subStatus": "Delivered_Other",
        "carrier": "DHL Paket"
    },
    "lastUpdate": "2026-10-14T19:42:00+02:00",
    "labelCreatedAt": "2026-10-10T18:03:00+02:00",
    "pickedUpAt": null,
    "deliveredAt": "2026-10-14T19:42:00+02:00",
    "daysAfterOrder": 5,
    "daysInTransit": 3,
    "daysSinceLastUpdate": 0,
    "estimatedDeliveryFrom": null,
    "estimatedDeliveryTo": null,
    "serviceType": "Shipment for Export",
    "weightKg": 0.75,
    "pieces": null,
    "dimensions": "0.19x0.12x0.11",
    "referenceNumber": null,
    "customerNumber": null,
    "localNumber": null,
    "localCarrier": null,
    "milestones": [
        {
            "stage": "InfoReceived",
            "time": "2026-10-10T18:03:00+02:00"
        },
        {
            "stage": "OutForDelivery",
            "time": "2026-10-14T08:48:00+02:00"
        },
        {
            "stage": "AvailableForPickup",
            "time": "2026-10-14T16:00:00+02:00"
        },
        {
            "stage": "Delivered",
            "time": "2026-10-14T19:42:00+02:00"
        }
    ],
    "eventCount": 10,
    "events": [
        {
            "time": "2026-10-14T19:42:00+02:00",
            "timeUtc": "2026-10-14T17:42:00Z",
            "description": "The shipment has been successfully delivered",
            "descriptionTranslated": null,
            "location": "PL",
            "stage": "Delivered",
            "subStatus": "Delivered_Other",
            "carrier": "DHL Paket"
        },
        {
            "time": "2026-10-14T16:00:00+02:00",
            "timeUtc": "2026-10-14T14:00:00Z",
            "description": "The shipment is ready for pick-up by the recipient. Please find more information here.",
            "descriptionTranslated": null,
            "location": "PL",
            "stage": "AvailableForPickup",
            "subStatus": "AvailableForPickup_Other",
            "carrier": "DHL Paket"
        }
    ],
    "lookupCode": 200,
    "lookupError": null,
    "trackingUrl": "https://t.17track.net/en#nums=CQ123456789DE",
    "scrapedAt": "2026-11-17T12:00:00.000Z"
}
```

### 📋 Dataset Views

The Apify Console gives you **3 ready-made table views** to quickly browse your results:

| View                        | What It Shows                                                                             |
| --------------------------- | ----------------------------------------------------------------------------------------- |
| 📊 **Overview**             | Number, status, carrier, from and to country, last update, delivery date, days in transit |
| 📍 **Latest event**         | The newest checkpoint, ETA, last-mile carrier and a link to 17TRACK                       |
| 🔔 **Changes (monitoring)** | What changed since the previous run, with the previous status                             |

### ❓ FAQ

**🤔 Is there a limit like on the 17TRACK website?**
No. The website takes 40 numbers at a time; here you paste the whole list and it is split into batches for you.

**🤔 Do I need to know the carrier?**
No. The carrier is detected automatically from the tracking number, including both carriers of international parcels.

**🤔 What does "NotFound" mean? Am I charged for it?**
17TRACK has no information about that number yet: it may be too new or mistyped. You are charged only for parcels with tracking data, so "NotFound" rows are free.

**🤔 How many numbers can I track per run?**
As many as you like. Numbers are tracked in batches of 40, and thousands per run are fine.

**🤔 How do I get alerts when a parcel is delivered?**
Turn on "Monitor changes", schedule the run every few hours and add a webhook URL. You receive only parcels whose status or history changed.

**🤔 Can I export the data?**
Yes — JSON, CSV, Excel, XML, HTML, RSS. You can also push data directly to Google Sheets, Zapier, Make, or any webhook/API endpoint.

**🤔 How often should I run this?**
For fresh data, run daily or weekly. You can schedule automatic runs on Apify with just a few clicks.

**🤔 Does it work with proxies?**
Yes — residential proxies are recommended for the best results. The scraper works with Apify's built-in proxy service.

### 🛠️ Need Custom Filters or Features?

**I'm happy to customize this tool for your specific needs!** 🤝

Whether you need:

- 🎯 Additional filters (only delayed parcels, only exceptions, only a given carrier or country)
- 📊 Extra data fields or custom output formats
- 🔄 Integration with your shop, CRM, Google Sheets, or database
- ⏰ Scheduled tracking with automatic deduplication
- 🌐 Tracking directly on carrier websites alongside 17TRACK

👉 **Don't hesitate to reach out via private message** — I respond quickly and I'm always open to building exactly what you need. No request is too small or too specific!

### ⚖️ Legal & Ethical Use

This tool reads **only publicly available tracking information** that anyone can see on 17TRACK by entering a tracking number. It does not log in, access accounts or collect personal data such as names or street addresses. Please track only parcels you are entitled to follow and use the data in compliance with applicable laws.

# Actor input Schema

## `trackingNumbers` (type: `array`):

Parcel tracking numbers, one per line. Any carrier: postal services (China Post, USPS, Royal Mail, Poczta Polska, ...), couriers (DHL, UPS, FedEx, DPD, GLS, ...) and e-commerce lines (Cainiao, YunExpress, 4PX, ...). The carrier is detected automatically. 17TRACK result links work too.

## `carrier` (type: `string`):

Leave on "Detect automatically" for mixed lists. Pick a carrier when 17TRACK cannot recognise your numbers (status CarrierNotDetected): every number in this run is then looked up with that carrier.

## `includeEvents` (type: `boolean`):

Add every tracking event (time, location, description, carrier) to each package. Turn off if you only need the current status.

## `onlyFound` (type: `boolean`):

Leave out numbers 17TRACK has no information about yet. Those rows are free either way.

## `excludeEmptyFields` (type: `boolean`):

Remove fields without a value from each row for a leaner export.

## `monitorChanges` (type: `boolean`):

Remember earlier runs and return only packages that are new or have news: a new status (for example In transit → Out for delivery → Delivered) or a new tracking event. Each row says whether the status changed and what it was before. Schedule the same list every few hours.

## `stateKey` (type: `string`):

Optional name for the remembered list, so several schedules keep separate histories. Leave empty to derive it from the numbers.

## `emitUnchanged` (type: `boolean`):

In monitoring mode, return every package, not only new or changed ones.

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

Optional URL that receives a POST with the new and changed packages after each run (Zapier, Make, n8n, your shop or CRM).

## `maxConcurrency` (type: `integer`):

How many batches of 40 numbers are tracked at the same time. 2 handles thousands of numbers per run.

## `startUrls` (type: `array`):

Alternative to "Tracking numbers" for integrations that send URLs, e.g. https://t.17track.net/en#nums=RR123456785CN. Both lists are combined.

## `proxyConfiguration` (type: `object`):

Apify Proxy keeps tracking reliable on large lists. Switch to residential proxies if many batches report a verification check.

## Actor input object example

```json
{
  "trackingNumbers": [
    "RR123456785CN",
    "1Z999AA10123456784",
    "LX123456789CN"
  ],
  "carrier": "0",
  "includeEvents": true,
  "onlyFound": false,
  "excludeEmptyFields": false,
  "monitorChanges": false,
  "emitUnchanged": false,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "trackingNumbers": [
        "1Z999AA10123456784"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("trev0n/17track-scraper").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 = { "trackingNumbers": ["1Z999AA10123456784"] }

# Run the Actor and wait for it to finish
run = client.actor("trev0n/17track-scraper").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 '{
  "trackingNumbers": [
    "1Z999AA10123456784"
  ]
}' |
apify call trev0n/17track-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,trev0n/17track-scraper"
        }
    }
}
```

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/Z4KuJgUe1BVeR6u4y/builds/CFKpE7C9bjTgv0dhT/openapi.json
