# FedEx Package Tracking Scraper & Status Lookup (`muhammadafzal/fedex-package-tracking-scraper`) Actor

Scrape public FedEx tracking pages in bulk and export normalized package status, delivery dates, service, locations, latest scans, and detailed tracking events to an Apify dataset. No FedEx account or cookies required.

- **URL**: https://apify.com/muhammadafzal/fedex-package-tracking-scraper.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Automation, E-commerce
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 fedex tracking records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## FedEx Package Tracking Scraper

Extract public FedEx package tracking records into an Apify dataset. Provide one or more FedEx tracking numbers or door-tag numbers and receive normalized status, delivery dates, service, origin/destination summaries, the latest scan, detailed scan events, and a canonical FedEx tracking URL.

The Actor uses the FedEx public tracker in a real browser and captures page-owned tracking responses. No FedEx account, OAuth token, cookies, or user login is required by default. FedEx may return an Akamai/WAF denial depending on network, geography, or traffic; in that case the Actor reports `BLOCKED` diagnostics and writes no fabricated record. This Actor does not bypass CAPTCHA, authentication, or access controls.

### Input

```json
{
  "trackingNumbers": ["794644790138", "449044304137"],
  "includeDetailedScans": true,
  "maxResults": 30
}
```

You can also paste newline-, comma-, or space-separated values into `trackingNumbersText`. Up to 30 unique values are accepted per run, matching FedEx's documented batch tracking limit. The default run uses one sample-shaped tracking number for easy configuration; replace it with a real number before relying on the output.

### Output

Each dataset item contains `tracking_number`, `status`, `status_code`, `status_detail`, `estimated_delivery_date`, `actual_delivery_date`, `service`, `ship_date`, `origin`, `destination`, `package_count`, `last_scan`, `scan_events`, `special_handling`, `tracking_url`, `source`, `scraped_at`, and `warnings`.

Run diagnostics are stored in `SUMMARY` and `OUTPUT`. Empty, blocked, rejected, and data-with-warnings outcomes are kept distinct in the terminal status.

### Pricing

Pay per event: $0.005 per unique schema-valid tracking record written to the default dataset. Actor start billing is configured separately by Apify. A blocked, empty, or rejected lookup does not create a result-item charge.

Use the data in accordance with FedEx terms and applicable law. This Actor is for public tracking information only and does not provide private shipment data, proof-of-delivery signature images, or authenticated FedEx API access.

### What data does FedEx Package Tracking Scraper return?

Results are written to the default Apify dataset or the output links declared by the Actor. Inspect the dataset schema and a small test run before building a production mapping.

### Use cases

- Schedule repeatable collection and export results to downstream workflows.
- Monitor public products, prices, availability, sellers, and catalog changes.
- Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
- Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
- Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

### Run FedEx Package Tracking Scraper with the Apify API

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/fedex-package-tracking-scraper').call({
  "trackingNumbers": [
    "794644790138"
  ],
  "trackingNumbersText": "",
  "includeDetailedScans": true,
  "maxResults": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

### Responsible use

Use this Actor only for data you are authorized to access. Follow the target website's terms, robots and access policies, and applicable privacy, database, copyright, anti-spam, and data-protection laws. Do not use it to bypass authentication or other access controls, collect private data, harass people, or make high-impact decisions without independent verification.

### Support

When reporting a problem, include the **Actor run ID**, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

### Frequently asked questions

#### Can I schedule FedEx Package Tracking Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

#### How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

#### How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

#### Can an AI agent call this Actor?

Yes. Add `muhammadafzal/fedex-package-tracking-scraper` through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

# Actor input Schema

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

Use this for one or more FedEx tracking or door-tag numbers. Enter up to 30 values; for example 794644790138. Whitespace and duplicate values are removed.

## `trackingNumbersText` (type: `string`):

Optional newline, comma, or space-separated FedEx numbers. Use this when importing a pasted list; for example 794644790138, 449044304137.

## `includeDetailedScans` (type: `boolean`):

Request and return the complete public scan-event history when FedEx provides it.

## `maxResults` (type: `integer`):

Maximum unique tracking records to return. Use 1–30; the default is 30.

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

Optional Apify Proxy configuration for FedEx WAF reliability. Direct access is the default; enable Apify Proxy when your account has proxy access.

## Actor input object example

```json
{
  "trackingNumbers": [
    "794644790138"
  ],
  "trackingNumbersText": "",
  "includeDetailedScans": true,
  "maxResults": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `records` (type: `string`):

Default dataset URL containing schema-valid tracking records.

## `warnings` (type: `string`):

Key-value summary URL containing non-fatal warnings and access diagnostics.

# 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": [
        "794644790138"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/fedex-package-tracking-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": ["794644790138"] }

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/fedex-package-tracking-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": [
    "794644790138"
  ]
}' |
apify call muhammadafzal/fedex-package-tracking-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammadafzal/fedex-package-tracking-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/dbqVIpvQ6rzAlzwew/builds/EnGGaj0QQO9NduXac/openapi.json