Skip to main content
FedEx Freight (SCAC: FXFE) hosts its LTL fuel surcharge page behind Cloudflare’s anti-bot protections. Direct httpx requests and residential proxies are rejected before the origin is reached. NexusFeed bypasses the block by routing every FedEx extraction through ScraperAPI’s render API in ultra_premium mode with country_code=us, which presents the request as a residential browser session and loads the page successfully.

Carrier overview

Why the render API

FedEx’s fuel surcharge page is served with Cloudflare’s JavaScript challenge. NexusFeed attempted:
  • Direct httpx → blocked
  • Residential proxy → blocked
  • Standard ScraperAPI render → partial response, HTML not hydrated
  • ultra_premium + render + country_code=us → success
The last configuration reliably returns the fully rendered HTML. Every FedEx call burns more ScraperAPI credits than, say, ODFL or Averitt, which is part of why the LTL product is priced as a flat $0.03 per request across all carriers — FedEx requests are subsidized by cheaper carriers.

Example request

Example response

FedEx’s doe_diesel_price_usd is always null. The upstream tariff page publishes the surcharge percentage and effective date, but does not disclose the DOE #2 diesel trigger. Confidence is scored against effective_date and fuel_surcharge_pct only.

Use cases

  • Auditing FedEx Freight LTL invoices for the current week.
  • Quoting shipments moving on FedEx Freight where a live surcharge is required.
  • Including FedEx in multi-carrier carrier selection for lanes where it is a realistic option.