DHL Tracking Scraper — Package Status, ETA & Checkpoints
Pricing
from $17.00 / 1,000 tracked dhl shipments
DHL Tracking Scraper — Package Status, ETA & Checkpoints
Track up to 10 DHL packages per run: status, delivery estimate, location and checkpoint history, with no DHL API key. USD 20 per 1,000 shipment records.
Pricing
from $17.00 / 1,000 tracked dhl shipments
Rating
0.0
(0)
Developer
Muhammad Afzal
Maintained by CommunityActor stats
0
Bookmarked
6
Total users
3
Monthly active users
14 days ago
Last modified
Categories
Features
Share
DHL Tracking Scraper looks up as many as 10 DHL tracking numbers per run on DHL's public tracker and returns status, estimated delivery, origin and destination, current location, service and the full checkpoint history as one JSON record per tracking number. It is built for ecommerce, logistics and customer-support teams that track DHL packages in batches, and costs USD 20 per 1,000 shipment records on the FREE tier, charged only for records delivered.
No DHL account or developer key is needed. If you have a DHL developer key, the Actor can use DHL's official tracking API instead.
How do I track DHL packages without a DHL API key?
Paste up to 10 tracking numbers and run with accessMode set to auto. demoMode only applies to DHL's sample number 7777777770, so real numbers are tracked even if it stays on. Without a key, Auto mode opens DHL's public tracking page in a headless browser and reads the tracking response it loads. Spaces, commas and semicolons inside a number are removed, duplicates are dropped, and IDs must be 5–50 letters, digits or hyphens.
{"trackingNumbers": ["00340434292135100186", "JD014600006281234567"],"demoMode": false,"accessMode": "auto","language": "en","requesterCountryCode": "US","includeRaw": false}
| Input | Default | Notes |
|---|---|---|
trackingNumbers | ["7777777770"] | 1–10 DHL tracking IDs |
demoMode | true | Returns DHL's sample shipment for 7777777770 as one record labelled isDemoData: true; ignored when no number is the sample |
accessMode | auto | auto (website, or API when a key is given), website, or api |
dhlApiKey | empty | Optional DHL developer key; stored as a secret |
recipientPostalCode | empty | Destination postal code; only with a single tracking number |
language / requesterCountryCode | en / US | Localize DHL's status text and tracking page |
includeRaw | false | Attach DHL's original shipment object in raw |
The prefill runs DHL's documented sample number in demo mode, so a first run shows the output shape. The sample is not a real shipment: it is saved as one dataset record labelled isDemoData: true (shown in the Demo data column) and is charged like any record.
What DHL tracking data does it return?
Each tracking number becomes at most one record. DHL hides some fields for some services and destinations; those come back as null.
| Field | What it means |
|---|---|
trackingNumber | The number you entered |
shipmentId | DHL's shipment ID for this record |
service / productName | DHL business unit (for example express, ecommerce, dsc) and product |
status / statusCode / description | Current status text, DHL status code (for example pre-transit, transit, delivered, failure) and detail |
statusTimestamp | When DHL recorded the current status |
estimatedDelivery | DHL's delivery estimate when shown |
originCountryCode / originPostalCode / originCity | Origin details |
destinationCountryCode / destinationPostalCode / destinationCity | Destination details |
currentLocation | Latest checkpoint location |
totalPieces | Number of pieces |
events | Checkpoint history: timestamp, status code, status, description, location |
serviceUrl / sourceUrl | DHL service link and the public tracking page for the number |
retrievedAt / isDemoData / raw | Lookup time, demo flag, optional original object |
When DHL matches one number to several shipments (in an owner test, the generic number 1234567890 matched 12 supply-chain shipments through customer references), the Actor returns and charges one record: the shipment whose ID equals the number, or DHL's first match. SUMMARY notes how many shipments DHL matched, so use the full tracking number to choose a specific one.
A SUMMARY record in the key-value store gives requested, delivered, empty, blocked and failed counts, the access route used and one warning per number without a record or with several DHL matches.
When should you use DHL Tracking Scraper, and when not?
Use it when your numbers are DHL and you want checkpoint-level history for support tickets, delivery-exception reports or a daily shipment audit, including DHL's supply-chain and eCommerce IDs that the unified tracker covers.
Pick a different tool when:
- Your numbers are FedEx. Use FedEx Tracking Scraper.
- Your numbers are UPS. Use UPS Tracking Scraper.
- Your list mixes UPS and FedEx. Use Multi-Carrier Package Tracking.
- You need postal services or other carriers. 17TRACK Package Tracking Scraper reads 17TRACK's public tracker.
- You need labels, rates, pickups, proof-of-delivery documents or push notifications. Use DHL's authenticated business tools.
Can I use my own DHL tracking API key?
Yes. Paste your DHL Shipment Tracking (Unified) consumer key from developer.dhl.com into dhlApiKey. In auto mode the key switches the run to DHL's official API; api mode requires it. The Actor waits about five seconds between numbers in API mode to stay inside DHL's rate limits. The key is a secret input and is never written to records, logs or SUMMARY.
How do I check DHL tracking status automatically every day?
Save your input as a task and attach an Apify schedule. Each run writes a fresh dataset you can export, send to a webhook, or read from code:
JavaScript (apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('muhammadafzal/dhl-package-tracking-scraper').call({trackingNumbers: ['00340434292135100186'],demoMode: false,accessMode: 'auto',});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.map((i) => [i.trackingNumber, i.status, i.estimatedDelivery]));
Python (apify-client):
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ["APIFY_TOKEN"])run = client.actor("muhammadafzal/dhl-package-tracking-scraper").call(run_input={"trackingNumbers": ["00340434292135100186"], "demoMode": False, "accessMode": "auto"})for item in client.dataset(run.default_dataset_id).iterate_items():print(item["trackingNumber"], item["status"], item["currentLocation"])
Use it from an AI assistant
DHL Tracking Scraper works from Claude, ChatGPT, Cursor or any MCP client through Apify's MCP server. Add https://mcp.apify.com/?tools=muhammadafzal/dhl-package-tracking-scraper as a server, then ask, for example: "Track these six DHL numbers and tell me which ones have a failed delivery attempt and where they are now." Real numbers are tracked even if the agent leaves demoMode on.
What does the output look like?
Two records from an owner test of the public-website route, shortened:
[{"trackingNumber": "1234567890","shipmentId": "SeLECT Upgrade TMS/169182707","service": "dsc","productName": "Transport Order","statusCode": "delivered","status": "Delivered","description": "Shipment Proof of Delivery","statusTimestamp": "2026-06-25T05:25:00+03:00","estimatedDelivery": null,"currentLocation": "Kuwait,Kuwait","events": [{ "timestamp": "2026-06-25T05:25:00+03:00", "statusCode": "delivered", "status": "Delivered", "description": "Shipment Proof of Delivery", "location": "Kuwait,Kuwait" },{ "timestamp": "2026-06-25T04:32:00+03:00", "statusCode": "transit", "status": "Dispatched", "description": "Shipment Pick-Up", "location": "KUWAIT CITY,Kuwait" }],"sourceUrl": "https://www.dhl.com/global-en/home/tracking.html?tracking-id=1234567890","retrievedAt": "2026-09-28T19:50:29.889Z","isDemoData": false,"raw": null},{"trackingNumber": "1234567890","shipmentId": "Centiro/218000385","service": "dsc","statusCode": "failure","status": "Delivery Failed","events": ["... five checkpoints ..."],"isDemoData": false}]
How much does DHL tracking cost? Pricing
You pay per delivered shipment record plus a start fee. Apify platform usage is included. Numbers that are blocked, not found or rejected write no records and pay no record events. The demo-mode sample is one record, labelled isDemoData: true, and is charged like any record.
| Event (USD) | FREE | BRONZE | SILVER | GOLD, PLATINUM, DIAMOND |
|---|---|---|---|---|
| Tracked DHL shipment | 0.020 | 0.020 | 0.020 | 0.017 |
| Actor start, per started GB of allocated memory | 0.00005 | 0.00005 | 0.00005 | 0.00005 |
The default memory is 512 MB, which website lookups need, so a run pays one start event.
- 10 numbers with one shipment each, FREE tier: USD 0.00005 + 10 × 0.020 = USD 0.20.
- 10 numbers every day for 30 days, GOLD tier: 30 × (USD 0.00005 + 10 × 0.017) = USD 5.10.
What if DHL blocks a lookup or finds no shipment?
The run still finishes, and only real DHL tracking responses become records. A number DHL does not recognize is reported as empty, an access challenge that cannot be passed is reported as blocked, and a page that never returns a tracking response is reported as failed. Each case appears in SUMMARY and is not charged. The Actor does not solve CAPTCHAs or bypass access controls.
New DHL numbers often show events only 24–48 hours after DHL receives the shipment. Website lookups run one at a time in one browser session. The first number takes about 10–30 seconds while DHL checks the session, and later numbers a few seconds each, so a batch of 10 usually finishes in about a minute, well inside the 300-second default timeout. If the timeout gets close, the run stops before the next number, writes SUMMARY and charges only the records it delivered.
FAQ
Do I need a DHL developer account?
No. Auto and website modes read DHL's public tracker. A developer key is optional and switches the run to DHL's official API.
Why did my run return a sample shipment?
demoMode is on by default and returns DHL's sample response for 7777777770 as one charged record labelled isDemoData: true. It is ignored when none of your numbers is the sample, so real packages are tracked normally. Mixing 7777777770 with real numbers while demoMode is on is rejected, so sample data never lands among real results.
Does it track DHL Express and DHL eCommerce numbers?
It returns whatever DHL's unified tracker returns for the number, across DHL business units. The service field shows which unit answered.
Can I export DHL tracking results to Excel?
Yes. Export the dataset as Excel, CSV or JSON from Apify Console, or send it to Google Sheets with Make, Zapier or n8n.
What if one number matches several DHL shipments?
This usually happens when the number is also a customer reference. The Actor returns and charges one record for that number (the exact ID match, or DHL's first match) and notes the number of matches in SUMMARY. Use the full DHL tracking number to get a specific shipment.
How many DHL numbers can I track per run?
Up to 10. Start several runs from the API or a schedule for longer lists.
Related Actors
- FedEx Tracking Scraper: bulk FedEx status and scan history.
- UPS Tracking Scraper: bulk UPS and InfoNotice tracking.
- Multi-Carrier Package Tracking: mixed UPS and FedEx lists.
- 17TRACK Package Tracking Scraper: other carriers through 17TRACK's public tracker.
Legal and privacy note
Track only shipments you send, receive or are authorized to monitor, and follow DHL's terms and applicable privacy law. Tracking records can include delivery locations, so keep datasets private and delete them when no longer needed. This Actor reads public tracking data or uses your own DHL key, and does not bypass authentication. It is unofficial and not affiliated with DHL; the DHL name identifies the source.
Last verified: 2026-11-03