Reference · built on requestConnectorShipping & logistics

FedEx

Tracking, rates, transit times, address validation, shipments, and pickups from the FedEx REST APIs.

Request accessPricing ↗

About

FedEx runs a global express, ground, and freight network and publishes REST APIs on the FedEx Developer Portal. The Track API returns scan events, the latest status, an estimated delivery time window, and delay reasons for up to 30 tracking numbers per request. The Rates and Transit Times API quotes LIST, ACCOUNT, PREFERRED, and INCENTIVE rates with surcharges itemized. The Ship API creates shipments, labels, return tags, and customs documents.

An operator on Fibric reads FedEx tracking against your open orders, flags a shipment whose delay reason or delivery window breaks the promise you made, and proposes a return tag, a pickup, or an address correction for your approval.

This is a reference listing. It documents what Fibric would read from FedEx and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Scan events, latest status, and the estimated delivery time window from the Track API, up to 30 tracking numbers per request
  • Delay details with reasons, signature images, and Signature Proof of Delivery documents through Track Document
  • Track by References: a purchase order, invoice, bill of lading, or part number instead of a tracking number
  • LIST, ACCOUNT, PREFERRED, and INCENTIVE rate quotes with surcharges, discounts, fees, and taxes itemized
  • Transit times and delivery commitments for FedEx Express, FedEx Ground, and FedEx Home Delivery
  • Resolved addresses with business, residential, or mixed classification and Delivery Point Valid status, up to 100 per request
  • Pickup availability by postal code for FedEx Express and FedEx Ground

Proposed actions

  • Target capability: propose a shipment through Create Shipment, with the label, tracking number, and any commercial invoice attached for review
  • Target capability: propose a return label through Create Tag, or cancel one through Cancel Tag before it is picked up
  • Target capability: propose a pickup through Create Pickup, or cancel a scheduled one through Cancel Pickup
  • Target capability: propose cancelling a shipment through Cancel Shipment using its tracking number and account

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch a delayed package before the customer asks

    Read delay details and the estimated delivery time window for every open shipment. When a package will miss its promise date, propose the customer notice and a note on the order.

    With Carrier Exception, Stalled Shipment

  • Fix a bad address before the label prints

    Resolve the ship-to address and its residential or business classification. Propose the corrected address for approval when Delivery Point Valid fails.

    With Address Repair

  • Settle a delivery dispute with the signature

    Pull the Signature Proof of Delivery document for a contested delivery and attach it to the support conversation.

    With Delivery Dispute

Requirements

  • A FedEx account, associated to your organization on the FedEx Developer Portal by a portal administrator
  • A Developer Portal project with an API Key and Secret Key for the APIs you use
  • For Compatible, Integrator, or Proprietary Parent Child customers, a child_key and child_secret as well
  • Shipper and recipient addresses, service type, and packaging details for every rate or ship request
Authentication
OAuth 2.0 client credentials: POST /oauth/token with the project's API Key as client_id and API Secret Key as client_secret; tokens expire after 3600 seconds.

Limits

  • Track API responses are pulled on request; pushed events need FedEx Advanced Integrated Visibility, billed by tracking numbers processed per month
  • Access tokens last one hour and must be regenerated
  • Pickup requests cannot be modified; cancel and resubmit. FedEx asks for one dispatch request per day per location
  • Address Validation does not determine deliverability: FedEx does not deliver to every valid address

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request FedEx ↗

Questions and answers

Does FedEx push tracking events, or does Fibric poll?
The Track API is request-based: you send up to 30 tracking numbers and get the latest status and scan events. Pushed updates come from FedEx Advanced Integrated Visibility, a separate webhook-based product billed by tracking numbers processed per month.
What credentials does the FedEx API need?
A project on the FedEx Developer Portal with an API Key and Secret Key, exchanged at POST /oauth/token for a bearer token. A FedEx account must be associated to the organization. Some customer types also send a child_key and child_secret.
Can Fibric schedule a FedEx pickup?
Yes, as a proposal. The Pickup Request API checks availability, creates a pickup for FedEx Express or FedEx Ground, and cancels one. FedEx asks for one dispatch request per day per location; a request cannot be edited, only cancelled and resubmitted.
Ask about FedEx

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with FedEx through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy