direct.ship-api.com/fedex

FedEx via Ship-API Direct

Direct is a proxy in front of FedEx. Instead of calling FedEx directly, you point the same request at Ship-API Direct. We forward it to FedEx and inject the carrier credentials and account configuration where needed, so your integration carries one set of keys instead of one per carrier.

Base URL

Take the carrier name onto the Direct host. Every FedEx request goes through this base:

Base URL

https://direct.ship-api.com/fedex

Authentication

Every request must include the Ship-API authorization header, in addition to the normal FedEx headers.

Header

ship-api-authorization: Bearer YOUR_SHIP_API_KEY

This header is required in addition to the normal FedEx authentication headers.

You do not call FedEx's own OAuth and credential APIs. You hit the Direct endpoints below with your Ship-API key, and Ship-API exchanges credentials with FedEx for you.

How requests work

Use the normal FedEx API paths. The only change is the host. FedEx uses OAuth 2.0, so for an access token, instead of calling FedEx directly you call:

OAuth token

POST https://direct.ship-api.com/fedex/oauth/token

And for a rate quote:

rate quote

https://direct.ship-api.com/fedex/rate/v1/rates/quotes

Paths mirror FedEx's own API. Whatever FedEx endpoint you call, keep the path and swap the host for the Direct base above.

Build against the FedEx Web Services interface reference and point the same calls at Direct.

Example request

The request body and normal FedEx headers stay the same; the ship-api-authorization header is added on top.

POST

POST https://direct.ship-api.com/fedex/rate/v1/rates/quotes

Authorization: Bearer FEDEX_ACCESS_TOKEN
ship-api-authorization: Bearer YOUR_SHIP_API_KEY
Content-Type: application/json

How Ship-API handles the request

You send the request to the Direct base URL with the normal FedEx API path:

Request URL

https://direct.ship-api.com/fedex/{fedex-api-path}

Ship-API then forwards the request to FedEx. Where required, it injects or manages the FedEx-specific credentials and settings. This can include:

FedEx client ID
FedEx client secret
FedEx shipper account number
Other agreed FedEx configuration

You do not need to send these values unless specifically agreed.

Summary

Use the Direct URL with fedex in the path, keep the normal FedEx API structure, and add the ship-api-authorization header to every request. Ship-API handles the carrier-specific configuration and forwards the request to FedEx.

Open Direct Get a Ship-API key Back to Direct