FedEx · Authentication Profile

Fedex Authentication

Authentication

FedEx declares 1 security scheme(s) across its OpenAPI definitions.

Address ValidationFreightLogisticsPickupRatingsShippingTrackingWebhookFortune 100
Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

oauth2 oauth2

Source

Authentication Profile

Raw ↑
generated: '2026-11-05'
method: searched
source: https://developer.fedex.com/api/en-us/catalog/authorization/v1/docs.html
docs: https://developer.fedex.com/api/en-us/catalog/authorization/v1/docs.html
summary: 'OAuth 2.0 bearer tokens. Every FedEx API request carries an authorization header holding a token obtained from POST https://apis.fedex.com/oauth/token (sandbox: https://apis-sandbox.fedex.com/oauth/token) with the API Key (client_id) and Secret Key (client_secret) issued per project in the Developer Portal. The published OpenAPI fragments model authorization as a required header parameter rather than a securityScheme; the oauth2 scheme in the working specs was added by API Evangelist from this documentation.'
schemes:
- name: oauth2
  type: oauth2
  flow: clientCredentials
  token_url: https://apis.fedex.com/oauth/token
  sandbox_token_url: https://apis-sandbox.fedex.com/oauth/token
  request_content_type: application/x-www-form-urlencoded
  grant_types:
  - client_credentials
  - csp_credentials
  - client_pc_credentials
  credentials:
    client_id: API Key received during FedEx Developer Portal registration
    client_secret: Secret Key received during FedEx Developer Portal registration
    child_Key: Customer Key - login credential for an Integrator, Compatible or Proprietary Parent Child customer (csp_credentials / client_pc_credentials)
    child_secret: Customer Secret paired with child_Key
  token_lifetime: An OAuth token is valid for an hour (Quotas & rate limits guide FAQ)
  header: 'authorization: Bearer <token>'
  scopes: []
  notes:
  - FedEx APIs do not support Cross-Origin Resource Sharing (CORS).
  - 'Best practices: cache the access token until an HTTP 401 is observed, then regenerate; never expose the token to the browser or end user; use TLS 1.2 or higher.'
  - 'Token-endpoint thresholds per public IP: burst 3 hits/second over 5 seconds, average 1 hit/second over 2 minutes; violation returns 403 for 10 minutes (see rate-limits/).'
  docs: https://developer.fedex.com/api/en-us/catalog/authorization/v1/docs.html
related:
  rate_limits: rate-limits/fedex-rate-limits.yml
  best_practices: https://developer.fedex.com/api/en-us/guides/best-practices.html

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/fedex-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.