FedEx
Book shipments and track deliveries with FedEx straight from your orders, with no re-typing.
19 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with FedEx, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create shipment and labelApproval by rule
- Track a FedEx multi-piece shipmentRead
Example flow
- FedEx · Track a FedEx multi-piece shipmentDone
- FedEx · Create shipment and labelNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches FedEx.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to FedEx
- FedEx's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a FedEx test account before you go live.
For developers
Technical detail
Quote parcel and Freight LTL rates, validate shipments and addresses, check pickup and service availability, read trade regulations, track and create FedEx shipments.
FedEx API docs- Source actions
- 19
- Destination actions
- 1
- Data types
- 20
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Address validations1
- Validate addressSource
Resolve and classify an address (business, residential or mixed).
Freight pickup availabilities1
- Check Freight LTL pickup availabilitySource
List FedEx Freight LTL pickup options for an address. Books nothing.
Freight rates1
- FedEx Freight LTL ratesSource
Quote FedEx Freight LTL rates and transit for a palletised shipment.
Locations1
- Find FedEx locationsSource
FedEx Office, ship centres, drop boxes and lockers near an address.
Pickup availabilities1
- Check pickup availabilitySource
List FedEx Express and Ground pickup options, cut-off times and access windows for an address. Books nothing.
Postal codes1
- Validate postal codeSource
Validate a postal code for a carrier and ship date and return the cleaned code.
Rates1
- Rate quotesSource
Rate quotes (list and account rates) and transit times for a shipment.
Regulatory details1
- Get trade regulatory detailsSource
Read the regulatory documents, statements and country advisories FedEx Global Trade lists for an international shipment.
Service options1
- Package and service optionsSource
Services, packaging and limits available between two locations.
Shipment results1
- Get async shipment resultsSource
Retrieve labels for a shipment FedEx processed asynchronously (by job ID).
Shipment validations1
- Validate shipmentSource
Check a shipment request against FedEx Ship rules without creating a shipment or label. Free.
Shipments1
- Create shipment and labelDestinationNot retried automaticallyApproval before production
Create a FedEx shipment and return tracking numbers and labels. Billable in production.
Special service options1
- Special service optionsSource
List shipment and package special services, signature options, return types and battery options available for a shipment.
Tracking associated shipments1
- Track a FedEx multi-piece shipmentSource
Track every piece of a multiple-piece (MPS or group MPS) shipment, or the return linked to an outbound shipment, from the master tracking number.
Tracking documents1
- Check FedEx tracking documentsSource
Check whether FedEx holds a signature proof of delivery, bill of lading or freight billing document for a package, as metadata.
Tracking events1
- List FedEx scan eventsSource
Every scan event for one FedEx tracking number, one record per event.
Tracking references1
- Track by referenceSource
Track shipments by purchase order, invoice, customer reference or other alternate reference within a ship-date range.
Tracking tcn1
- Track by Transportation Control NumberSource
Track government and military shipments by their Transportation Control Number.
Tracking1
- Track by tracking numbersSource
Status, dates and scan events for up to 30 FedEx tracking numbers.
Transit times1
- Services and transit timesSource
Available FedEx services with commit dates and transit times.
Access and limits
- Authentication
- FedEx project API key and secret key (OAuth client credentials)
- Plans and access
- Requires a FedEx Developer Portal project with the Rate, Address Validation, Track, Ship, Service Availability, Postal Code Validation and Locations APIs, and a FedEx shipping account. Production keys need FedEx approval of the project; Ship API production access requires label certification.
- Test environment
- Test keys work against apis-sandbox.fedex.com with test account numbers; sandbox labels are not billed.
- Rate limits
- Per-project quotas (for example 1,400 transactions per 10 seconds) with HTTP 429; tracking allows up to 30 tracking numbers per request.
- Pagination
- Single responses; FedEx operations are lookups or quotes.
- Provider events
- Advanced Integrated Visibility webhooks push tracking events (separate product). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- shipments.create is billable and FedEx has no idempotency key; Nexra never retries it. Shipment and pickup cancellation, pickup creation, Freight LTL shipping and pickups, and trade document upload are intentionally excluded.
- Global Trade documents are read through regulatory details (document lists and URLs); FedEx does not offer a read of uploaded trade documents.
- x-customer-transaction-id carries the Nexra correlation ID for support lookups; FedEx does not deduplicate on it.
- requestedShipment objects follow the FedEx JSON schema and are passed through after structural validation.
- The health check validates FedEx's headquarters address (942 South Shady Grove Road, Memphis TN 38120), so the project needs the Address Validation API.
- The locations response is documented by example only; Nexra maps the documented example fields.
- Tracking documents (signature proof of delivery, bill of lading, freight billing document) are returned as metadata only: type, format, count and size. The base64 content is dropped.
- Associated shipment tracking returns one page; FedEx documents pagingDetails in the request but no next-page token in the response.
- Track notifications (POST /track/v1/notifications) are excluded because they send emails to recipients. Ground End of Day close, Open Ship, consolidation, return tags and Trade Documents Upload are excluded as writes.
- FedEx publishes no account, invoice or billing read API in its developer catalog.
Developer reference
- Create the FedEx credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose FedEx, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/fedex and the Connections API.