FedEx publishes its rate books, weekly fuel tables and holiday surcharges in the open, then changes them on its own calendar. We turn that moving paperwork into dated rows on the cadence you set.
Plans from €169 a month · Free project assessment · Reply within 1 business day
CSV · Excel · JSON · XML · FTP · SFTP · Amazon S3 · Google Cloud
API, JSON feed or CSV, XLSX and JSON files
ScheduleOne-time, monthly, weekly, daily or 3 times a day
FedEx pages, filters, fields and a schedule
Built, monitored and repaired by our team
API, JSON feed or CSV, XLSX and JSON files
The site turns away plain automated clients across much of its estate, the rate books arrive as PDF and spreadsheet rather than as HTML, and the locator sits on a different host with its own grammar. That mix is exactly the work we take on: anti-bot handling, proxy rotation and CAPTCHA solving, document parsing that turns a rate workbook into typed rows, and one pass per country site so every row carries the market, currency, index and effective date it was really published under. We build the FedEx scraper, run it on your cadence, watch it and repair it when a table moves or a fee is renamed. Delivery is CSV, JSON, XLSX or an API endpoint with a documented schema and stable column names. We pace collection, keep to public pages and published documents, and send a paid sample before any larger commitment.
We extract FedEx data as dated rows. Each row carries the service, lane, zone, weight step, effective date, currency and country site it came from, because without those a tariff figure means nothing six weeks later.
What the carrier keeps private we leave alone. Negotiated account rates, invoices, shipment contents and a recipient's name, address or signature are not published, so we do not supply them, and we do not follow shipments a client has no standing to see.
Point of sale is part of the record here, not a display preference. The same week can carry three different fuel percentages depending on which FedEx document you open, because the index behind each differs. International express in Europe is priced off the Gulf Coast spot price for kerosene-type jet fuel and moves weekly. Regional economy services are priced off the European Commission automotive gas oil price in euros per litre, also weekly, with the new figure posted around the Friday before it takes effect. The British domestic surcharge runs monthly off the national statistics forecourt diesel price in pence per litre, with a stated one month lag between index month and billing month.
Publishing habits differ as much as the indexes. The British surcharge pages carry the full weekly history and the complete trigger ladder; the American fuel page shows two weeks plus a short slice of each table and pushes the rest into the Service Guide. Ground and home delivery ride diesel while everything else rides jet fuel, so two series on one page diverge inside the same week.
The location network is a dataset of its own and lives on a separate host. Addresses follow a locale, region, city and location id grammar, every local-language locale is mirrored in English, and branded branches add child pages per service - printing and copying, banners and signs, passport photos, packing supplies. As of September 2026 the United States directory currently reports about 23,167 locations.
FedEx Corporate Services runs fedex.com as a reference library rather than a storefront. There is no catalogue to page through and nothing to add to a basket: the public layer is a stack of rate books, tariff tables, service descriptions, regulatory lists and a store locator, republished on a calendar the carrier sets itself. Every market sits on its own path of the same domain - en-us, es-us, de-de, fr-fr, ja-jp, zh-cn, ar-ae and the rest - and each one carries a different subset of those documents under different path words, which is why a country by country pass is the only honest way to cover the carrier.
The numbers live in documents, not in pages. The FedEx Service Guide carries the terms of carriage and the fee definitions. The Standard List Rates workbook carries the grids themselves, split into United States, United States export, United States import and ground tabs, priced by service, by zone and by weight step. Around them sit retail rates, FedEx One Rate flat pricing, the delivery area and pickup area postcode tiers, the weekly fuel tables and a surcharge change sheet for the year ahead. Most are posted as a PDF and a spreadsheet at once, which is why a FedEx price feed is a parsing job as much as a crawl.
Shipment status is the one thing keyed to a single package rather than to a tariff. A tracking number returns a status, a scan history and a delivery schedule; the signature image, the full sender and recipient detail and everything behind a login stay with the parties to the shipment. That line matters, and we work on the public side of it.
Delivery: CSV, JSON or XLSX files, our API or a JSON feed. MCP server on request.
Full plan detailsParcel spend sits near the top of the controllable lines in an e-commerce cost model, and almost none of it is a single number. An invoice is a list rate, minus a negotiated discount, plus a fuel percentage that moved this week, plus whatever accessorial fired on that particular package. Teams that benchmark carrier contracts rebuild that stack from the published side, and to do it they need the list grid, the fuel table for the right week and the fee schedule that was live on the ship date.
Freight audit and parcel consulting firms are the heaviest users. They reprice historical shipments against current published rates to show a client what a renegotiation is worth, and that only works if the rate history is dated and complete. Logistics software vendors need the same grids to drive rate shopping inside a warehouse system. Retailers and marketplaces use the service and transit layer to promise a delivery date at checkout without calling a carrier on every page view.
Competing carriers and postal operators read the surcharge calendar rather than the base rates, because that is where policy shows: when a peak surcharge starts, how steep the holiday step is, which fee is new this year, which lane just moved a zone. Analysts and trade press follow the same series, and customs and compliance teams watch the restricted item lists and service alerts to know which destinations are effectively closed. None of it can be answered by a single snapshot; the value sits in the same document collected again and again with its effective date attached.
Learn how to use web scraping to solve data problems for your organization
Leveraging advances in technology, the AI-powered web scraper has skyrocketed in demand and is helping to expand capabilities by automating tedious daily tasks and speeding up data collection from thousands of websites several times over.
Web scraping is a method of obtaining web data by extracting it from pages of web resources with the help of a program, that is, in automatic mode. It is used to syntactically convert web pages into more usable forms.
If you specialize in machine learning, you need to feed large amounts of data to the algorithms. Web scraping is the easiest and the most efficient method of collecting the data from all over the Internet.
ScrapeIt is a managed web scraping agency. You name the services, lanes, countries and refresh rate; we write the crawler, run it on schedule, monitor it and fix it when the target moves. There is nothing to install and nothing to maintain on your side. You get documented output in the format you asked for, stable column names, and a named contact who knows the project. We also tell you plainly what is collectable and what is not before you commit to anything.
Still unsure? Write to info@scrapeit.io
Yes. The ScrapeIt FedEx API returns list rate grids by service, zone and weight step, weekly fuel percentages with their index values, demand surcharge bands, transit commitments and location hours as JSON from an endpoint we host, refreshed on the schedule you set. Every row carries the country site, currency and effective date it was published under. The same data also comes as CSV or XLSX files or straight into your database.
We take what the public layer holds: list rate grids by service, zone and weight, retail and flat rate pricing, weekly fuel percentages with their index values and trigger bands, demand surcharge amounts with their date ranges, accessorial and fee schedules, delivery and pickup area postcode tiers, service descriptions and commitments, restricted item lists by country, dated service alerts, and the locator with hours, coordinates and last pickup times. Negotiated account rates, invoices, shipment contents and anything behind a login are not published, so we do not supply them, and we collect no personal data about senders or recipients.
They run on different clocks. The general rate increase lands once a year in early January and is announced months ahead, with next year's rate book posted beside the current one. Fuel is weekly for American and international services and monthly for the British domestic surcharge. Peak demand surcharges are published as dated bands and revised during the season, and the residential demand charge is recalculated every week from the shipper's own volume. Weekly collection covers fuel and demand; a daily pass on the change pages catches a mid-season revision the day it appears; rate books need a check whenever a new effective date is announced.
Yes, and here it matters more than usual. Each country site carries its own documents under its own path words, its own currency and its own fuel methodology, so a single global table built from one market is wrong by construction. We run each market as its own pass and stamp every row with the site, language, currency, index used and effective date. Where one market publishes more history than another - the British surcharge pages carry the full weekly series while the American page carries only the current weeks - we say which series a row came from instead of blending them.
Yes. We collect only publicly available data - rate books, surcharge tables, service guides and the locator, everything a visitor can see on FedEx - and we collect it legally. We take public pages and published documents, defeat no access control, and follow no shipment a client cannot claim. Delivery is CSV, JSON, XLSX or a REST endpoint on your schedule, with a documented schema and stable column names.
You share your needs, expectations, and desired timeframe. We'll suggest the best solution based on your request and budget.
Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.
Once you approve the sample, we launch the project and start full data collection. We gather, filter, and structure the data for easy use, delivering it on time in your preferred format.
Our team manages ongoing processes, monitors website changes, and supports all data extraction cycles. We can also help integrate data into your systems or create dashboards to simplify analysis.
Tell us which sites, which fields and how often. A couple of lines is enough to start.
FedEx data from €169/month. Free project assessment, reply within 1 business day.