FedEx Location Finder Scraper

Scrape public FedEx Location Finder results by ZIP code, city, state, or address and receive normalized location records with address, phone, distance, operating hours, services, coordinates when available, and the source URL.

Input

Field	Description
query	Required ZIP code, city, state, or address, such as 10001 or New York, NY.
countryCode	Two-letter FedEx country code. Default: US.
locale	FedEx locator locale. Default: en.
radiusMiles	Search radius from 1 to 100 miles. Default: 50.
maxResults	Maximum records from 1 to 200. Default: 50.
service	none, dropoff, shipping-assistance, or pickup.
useApifyProxy	Optional Apify Proxy session for challenged direct access.

Example:

{ "query": "10001", "maxResults": 25, "service": "dropoff" }

Output

Each dataset item contains name, locationType, address, streetAddress, city, region, postalCode, countryCode, phone, latitude, longitude, distanceMiles, hours, services, sourceUrl, and scrapedAt. Run diagnostics are saved in the OUTPUT key-value record.

Pricing

Event	Price
Actor start	$0.00005
FedEx location	$0.001 per result

A 25-result run costs up to $0.02505 in event charges, excluding any optional platform/proxy usage charges configured by the account.

Reliability and limits

The Actor uses the public FedEx locator directly through a bounded Playwright session. It does not bypass authentication, CAPTCHAs, or access controls. Empty searches produce zero dataset records and an OUTPUT diagnostic; access challenges are reported as warnings rather than fabricated locations. The scraper is limited to 200 results per run.

Use the data in accordance with FedEx terms, applicable law, and the rights of individuals whose contact information may appear in public location listings.

Use cases

• Build public prospect lists and qualify organizations or professionals before responsible outreach.
• 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 Location Finder 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-location-finder-scraper').call({
  "query": "10001",
  "countryCode": "US",
  "locale": "en",
  "radiusMiles": 50,
  "maxResults": 50,
  "service": "none",
  "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 Location Finder 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-location-finder-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.

Recommended workflow

1. Define the smallest useful scope. Choose a representative public URL, query, identifier, or filter and keep the first result limit low.
2. Run and inspect. Check the run log, dataset item count, field coverage, source URLs, and live event or usage charges.
3. Validate downstream assumptions. Confirm nullable fields, deduplication keys, timestamps, and any locale-specific formats before importing records into another system.
4. Scale gradually. Increase limits or scheduling frequency only after the small run behaves as expected. Use Apify's maximum-cost and timeout controls to bound large jobs.
5. Monitor changes. Keep a small known-good input as a canary. If the source layout or API changes, compare the new dataset with a previously validated run and report the run ID when requesting support.

For recurring workflows, store the exact Actor input with your pipeline configuration. This makes runs reproducible and helps distinguish a source-data change from an input change.