Skip to main content
ABF Freight (SCAC: ABFS) is a subsidiary of ArcBest and one of the more challenging LTL carriers to extract reliably. Its fuel surcharge page is served as an AngularJS application and its origin is periodically hostile to direct scraping. NexusFeed uses a two-strategy approach: a passthrough proxy primary path, falling back to a full ScraperAPI render when the primary fails.

​
Carrier overview

​
Two-strategy extraction

1

Strategy A — passthrough proxy

The primary path sends an httpx GET to ABF’s public fuel surcharge page through a residential proxy with keep_headers=True, which preserves browser-like headers across the proxy hop. When ABF’s origin cooperates, this returns AngularJS HTML that NexusFeed parses directly.
2

Strategy B — ScraperAPI full render fallback

When the primary path fails (timeout, 403, empty response, or confidence below threshold), the router automatically re-runs the extraction through ScraperAPI’s full-render mode, which executes the AngularJS client-side and returns the hydrated HTML. The response reports extraction_method: scraper_api_fallback so you know the fallback ran.

​
Example request

​
Example response

ABF’s confidence ratio is calculated against effective_date and fuel_surcharge_pct only. doe_diesel_price_usd is not a required field because the upstream source does not publish it.

​
Use cases

  • Invoice audit against ABF’s published LTL rate (most common).
  • Procurement benchmarking — ABF is often bundled in RFPs alongside ODFL, Saia, and Estes.
  • Compliance use cases do not apply (ABF is not on any state-regulated tariff).