Shipping Location Finder (USPS, UPS, FedEx) avatar

Shipping Location Finder (USPS, UPS, FedEx)

Pricing

from $52.35 / 1,000 shipping locations

Go to Apify Store
Shipping Location Finder (USPS, UPS, FedEx)

Shipping Location Finder (USPS, UPS, FedEx)

Find nearby USPS, UPS, and FedEx locations by US ZIP code with normalized addresses, hours, services, coordinates, distance, and official source URLs.

Pricing

from $52.35 / 1,000 shipping locations

Rating

0.0

(0)

Developer

Muhammad Afzal

Muhammad Afzal

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Free plan limit: Free-plan users can receive up to 5 result records per run. Paid-plan and local/unknown runs retain the Actor's existing limits.

Find nearby USPS, UPS, and FedEx shipping locations from the carriers’ official US location directories. Enter a five-digit ZIP code and receive normalized records for post offices, carrier stores, authorized shipping outlets, drop-off partners, and other listed service points.

This Actor is designed for logistics apps, returns workflows, customer-support tools, local directory enrichment, and AI agents that need one consistent result shape across the three major US parcel carriers. Hosted USPS requests use the Actor's managed proxy route; buyers do not need to configure a proxy. UPS and FedEx requests use the official carrier directory pages.

What it extracts

FieldDescription
carrierUSPS, UPS, or FedEx
locationIdCarrier directory identifier
name, locationTypePublic location name and carrier-defined category
streetAddress, city, state, postalCodeNormalized US address fields
phonePublic location or carrier phone number, when listed
latitude, longitudeExact coordinates when exposed by the official directory
distanceMilesDistance from the query ZIP centroid
distanceIsApproximatetrue when distance is based on ZIP centroids
hoursWeekly carrier-published hours when available
servicesDrop-off or service information shown on the listing
sourceUrlOfficial carrier page used for the record
queriedZipCode, scrapedAtSearch provenance and collection timestamp

When to use it

Use this Actor when you need a bounded, repeatable location lookup by US ZIP code. It is a good fit for showing nearby return points, comparing carrier coverage, routing a customer to a staffed counter, or feeding normalized locations into another Actor or agent.

Do not use it as a routing engine, a guarantee that a location accepts a particular parcel, or a source of real-time holiday closures. Confirm time-sensitive services and opening hours on the linked carrier page before sending a customer to a location.

Input

FieldTypeDefaultNotes
zipCodestring10001Required five-digit US ZIP code
carriersarrayall threeAny combination of USPS, UPS, and FedEx
radiusMilesinteger101–25 miles
maxResultsinteger501–200 records across all carriers

Example input:

{
"zipCode": "10001",
"carriers": ["USPS", "UPS", "FedEx"],
"radiusMiles": 10,
"maxResults": 25
}

Run through the Apify API:

curl -X POST "https://api.apify.com/v2/acts/<username>~shipping-location-finder/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"zipCode":"10001","carriers":["USPS","UPS","FedEx"],"radiusMiles":10,"maxResults":25}'

The dataset can then be read through the run’s defaultDatasetId, while the OUTPUT key-value-store record contains per-carrier diagnostics.

Output example

{
"carrier": "FedEx",
"locationId": "TSSAA",
"name": "FedEx at Walgreens",
"locationType": "FedEx at Walgreens",
"streetAddress": "383 W 31st St",
"city": "New York",
"state": "NY",
"postalCode": "10001",
"countryCode": "US",
"phone": "(800) 463-3339",
"latitude": null,
"longitude": null,
"distanceMiles": 0,
"distanceIsApproximate": true,
"hours": null,
"services": [],
"sourceUrl": "https://local.fedex.com/en-us/ny/new-york/tssaa",
"queriedZipCode": "10001",
"scrapedAt": "2026-08-27T06:00:00.000Z"
}

Pricing

This Actor uses pay-per-event pricing. These are the current Apify Store event prices:

EventPrice (USD)When it is charged
shipping-location$0.002Shipping location — One schema-valid USPS, UPS, or FedEx location written to the default dataset.
apify-actor-start$0.00005Actor Start — Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). — Charged once per run.

Apify platform usage for this Actor run is included alongside the event prices above; no separate per-run platform-usage fee is passed to users.

This covers Apify platform usage for this Actor run. Other Apify products or usage outside this Actor run may still follow your account plan.

Reliability and limitations

UPS and FedEx expose server-rendered official directory pages, so the Actor fetches and parses those pages directly. It discovers carrier-owned city pages from the relevant state directory rather than relying on a third-party geocoder.

The official USPS locator is JavaScript-driven and protected by Akamai. The Actor uses one consistent Playwright session and a US residential proxy for that path. If USPS blocks the session, UPS and FedEx results are preserved and OUTPUT.carrierOutcomes identifies USPS as blocked. No fabricated USPS records are added and no result events are charged for missing records.

Distance is exact when a carrier exposes coordinates. Otherwise it is an approximation between the query and result ZIP centroids, and distanceIsApproximate is set to true. Carrier directory coverage, services, and hours can change without notice. The Actor limits nearby city discovery to 20 cities per run to keep runtime and cost bounded.

The Actor reads public carrier location pages and returns factual business-location information with a link to the official source. Follow the carriers’ terms, applicable law, and Apify’s policies. Do not use the data for spam, surveillance, or decisions involving sensitive personal information. Carrier names and trademarks belong to their respective owners; this Actor is not endorsed by USPS, UPS, or FedEx.

Support

If a carrier changes its directory markup, include the run ID, input ZIP code, affected carrier, and the OUTPUT diagnostic in your issue. Do not include Apify tokens, proxy URLs, cookies, or other secrets.