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

{
  "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

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.