Connect FedEx: live rates, labels, and tracking
Get the API Key and Secret Key from your FedEx Developer Portal project plus your 9-digit FedEx Account Number, paste them into Integration, test, map services, and start rating and shipping.
The FedEx connector gets live rates, buys labels, tracks shipments, and voids labels through the FedEx API, all against your own FedEx account. Rates and label charges are billed to the FedEx Account Number you fill in.
Prerequisites#
- A FedEx account with a 9-digit FedEx Account Number — rates and labels are billed to this account.
- Access to FedEx Developer Portal → My Projects, where the API Key and Secret Key for your project are shown.
- A decision on environment first: fill sandbox with true to test in the sandbox, or leave it blank to use production. Sandbox and production credentials do not mix — use the credentials that belong to the environment you pick.
Get your credentials#
- Get the API Key: go to FedEx Developer Portal → My Projects → your project → API Key. This API Key is the OAuth Client ID for your project — copy it exactly as shown.
- Get the Secret Key: in the same project, open Secret Key — this is the OAuth Client Secret. The full value is only shown in full when it is generated, so save it somewhere safe right away. If you lose it, generate a new one in the portal.
- Get the FedEx Account Number: go to fedex.com → My Profile → Account Management and copy your 9-digit shipping account number. Rates and labels will be billed to this account.
- Warning — keep projects separate: Track and Rate / Ship may belong to two separate Developer Portal projects, each with its own API Key and Secret Key. For one connection, always use the API Key and Secret Key from the same project. Mixing the Key from one project with the Secret from the other will fail.
Fill it into Integration#
- Open Integration → Connector Marketplace → FedEx → New connection.
- API Key: paste the API Key from FedEx Developer Portal → My Projects → your project. This is the OAuth Client ID for that project. It is stored as a secret and never echoed back.
- Secret Key: paste the Secret Key from the same project. Make sure it pairs with the API Key above — do not use the Secret Key from a different project, for example the Track project when this connection is for Rate / Ship. It is stored as a secret and never echoed back.
- FedEx Account Number: fill in your 9-digit shipping account number from fedex.com → My Profile → Account Management, for example 123456789. Double-check every digit — the test does not verify this number, but rates and labels are billed to it.
- Use sandbox — optional: fill in true to use the sandbox, or leave it blank to use production. Fill in true only together with sandbox project credentials; leave it blank only together with production project credentials.
Test the connection#
Click Test connection. The test only exchanges your API Key and Secret Key for an OAuth token to check that the credentials work in the environment you picked. It does not verify the FedEx Account Number and it does not quote a rate, so a passed test confirms the Key and Secret only — if the account number is wrong, rates and labels can still fail afterwards. If the test fails, note the error and check the FAQ below.
Mapping / pick a template#
FedEx needs no order mapping — it works on parcels, not orders. What you map here are services: map each FedEx service to your corresponding internal service (service mapping), and enable only the FedEx services you actually ship with. Rate shopping and label buying follow this mapping, so an order only quotes and buys the service you intended for it.
Activate#
After activation, the connection is available for rate shopping and label buying at ship time, tracking updates come back and land on the shipment, and labels you no longer need can be voided through the same connection. Watch the first few shipments in Runs / Logs — especially the first rate quote and the first label — before trusting it unattended.
FAQ#
Test fails with 401
The API Key or Secret Key is wrong, or the two were mixed across projects — for example the API Key from the Rate / Ship project paired with the Secret Key from the Track project. FedEx only accepts a Key and Secret that belong to the same project, so a mixed pair is rejected.
Open one single project in FedEx Developer Portal → My Projects, re-copy both its API Key and its Secret Key from that same project without extra spaces, replace both fields, and test again.
Sandbox and production credentials are mixed up
The environment and the credentials do not match. The sandbox field says one environment — true for sandbox, blank for production — but the API Key and Secret Key come from a project for the other environment, so FedEx refuses the token exchange.
Pick one environment and make everything match it: for testing, set Use sandbox to true and fill in the sandbox project credentials; for live shipping, leave Use sandbox blank and fill in the production project credentials. Then test again.
Test passes but rates or labels fail
The FedEx Account Number is wrong. The test only exchanges an OAuth token and never checks the account number, so a mistyped or wrong account still passes the test — the failure only shows up when a rate or a label tries to bill that account.
Verify the account at fedex.com → My Profile → Account Management, correct the FedEx Account Number field to the exact 9-digit number shown there, and try the rate quote or label again.
Label created but tracking never updates
Tracking updates arrive on the FedEx schedule, not instantly, so a new label can show no movement for a while. If the parcel was never handed to FedEx, there is also no scan to report yet.
Confirm the parcel was handed to FedEx first. If tracking still shows nothing after the parcel has entered the FedEx network, check Runs / Logs for tracking errors, and confirm the connection used for tracking holds the API Key and Secret Key from the Track project — not the Rate / Ship pair.