Nexra
All connectors
Implemented
Procurement, logistics & supply chain
FedEx logo

FedEx

Quote rates, validate addresses and postal codes, track packages, check transit times and service options, find locations and create FedEx shipments.

Quote and ship with FedEx from order and ERP flows, and push tracking events back to customers and service teams.

Build a flow with FedExProvider API documentation

Source actions

8

Destination actions

1

Data types

9

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

address validations
  • Validate address
    Source

    Resolve and classify an address (business, residential or mixed).

    address_validations.search
locations
  • Find FedEx locations
    Source

    FedEx Office, ship centres, drop boxes and lockers near an address.

    locations.search
postal codes
  • Validate postal code
    Source

    Validate a postal code for a carrier and ship date and return the cleaned code.

    postal_codes.search
rates
  • Rate quotes
    Source

    Rate quotes (list and account rates) and transit times for a shipment.

    rates.search
service options
  • Package and service options
    Source

    Services, packaging and limits available between two locations.

    service_options.search
shipment results
  • Get async shipment results
    Source

    Retrieve labels for a shipment FedEx processed asynchronously (by job ID).

    shipment_results.get
shipments
  • Create shipment and label
    Destination
    Not retried automatically
    Approval before production

    Create a FedEx shipment and return tracking numbers and labels. Billable in production.

    shipments.create
tracking
  • Track by tracking numbers
    Source

    Status, dates and scan events for up to 30 FedEx tracking numbers.

    tracking.search
transit times
  • Services and transit times
    Source

    Available FedEx services with commit dates and transit times.

    transit_times.search

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). Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • shipments.create is billable and FedEx has no idempotency key; Nexra never retries it. Cancelling shipments, pickups and trade documents upload are not implemented.
  • 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.

Developer reference

  1. Create the FedEx credentials described above with the narrowest permissions your flows need.
  2. 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
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
FedEx docsAPI referenceFedEx docsAuthenticationFedEx docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/fedex and the Connections API.