# FedEx Location Finder Scraper (`muhammadafzal/fedex-location-finder-scraper`) Actor

Scrape public FedEx Location Finder results by ZIP code, city, state, or address with normalized addresses, phones, hours, services, distance, and source URLs.

- **URL**: https://apify.com/muhammadafzal/fedex-location-finder-scraper.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 fedex locations

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 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:

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

```javascript
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.

# Actor input Schema

## `query` (type: `string`):

Use this to search FedEx locations by ZIP code, city, state, or address. Example: 10001 or New York, NY.

## `countryCode` (type: `string`):

Two-letter country code for the FedEx locator. Example: US. Default: US.

## `locale` (type: `string`):

FedEx locator language/locale path. Example: en. Default: en.

## `radiusMiles` (type: `integer`):

Search radius sent to the FedEx locator. Use 1–100 miles. Default: 50.

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

Maximum locations to return. Use 1–200. Default: 50.

## `service` (type: `string`):

Optional FedEx service intent filter. Default: none.

## `useApifyProxy` (type: `boolean`):

Use an Apify Proxy session when direct access is challenged. Default: false.

## Actor input object example

```json
{
  "query": "10001",
  "countryCode": "US",
  "locale": "en",
  "radiusMiles": 50,
  "maxResults": 50,
  "service": "none",
  "useApifyProxy": false
}
```

# Actor output Schema

## `summary` (type: `string`):

Structured run diagnostics stored in OUTPUT.

## `results` (type: `string`):

Schema-valid FedEx location records.

# 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 = {
    "query": "10001",
    "countryCode": "US",
    "locale": "en",
    "service": "none"
};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/fedex-location-finder-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 = {
    "query": "10001",
    "countryCode": "US",
    "locale": "en",
    "service": "none",
}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/fedex-location-finder-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 '{
  "query": "10001",
  "countryCode": "US",
  "locale": "en",
  "service": "none"
}' |
apify call muhammadafzal/fedex-location-finder-scraper --silent --output-dataset

```

## MCP server setup

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