FedEx

FedEx API Authorization

Leverage the FedEx OAuth 2.0 token authentication method to authorize the application and authenticate API requests.

GitHub OpenAPI

Operations 1

POST /oauth/token Issue OAuth 2.0 access token #

Documentation

📖
Documentation
https://developer.fedex.com/api/en-us/catalog/authorization/v1/docs.html

Specifications

⚙
OpenAPI
https://artifacts.apis.io/fedex/openapi/fedex-authorization-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/fedex/json-schema/fedex-full-schema-schema.json
📊
JSONSchema
https://artifacts.apis.io/fedex/json-schema/fedex-response-schema.json

Other Resources

🔗
Summary
https://developer.fedex.com/api/en-us/catalog/authorization.html
🔗
APIsJSON
https://artifacts.apis.io/fedex/apis.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/fedex:fedex-api-authorization"
All apis 
curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

OpenAPI Specification

fedex-authorization-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: FedEx Track Authorization API
  version: 1.0.0
  description: 'OpenAPI 3.1 specification covering the FedEx OAuth 2.0 token endpoint and

    the core FedEx Track API v1 operations as documented on the FedEx Developer

    Portal (https://developer.fedex.com/api/en-us/catalog/track/v1/docs.html).

    Includes tracking by tracking number, tracking by reference,

    tracking by Transportation Control Number (TCN), associated shipments,

    document retrieval, and shipment notifications. Schemas are intentionally

    permissive to remain compatible with the live FedEx payloads; consult the

    FedEx Developer Portal for full payload field definitions.'
  contact:
    name: FedEx Developer Portal
    url: https://developer.fedex.com/
servers:
- url: https://apis.fedex.com
  description: Production
- url: https://apis-sandbox.fedex.com
  description: Sandbox / test environment
security:
- bearerAuth: []
tags:
- name: Authorization
  description: OAuth 2.0 token issuance for FedEx APIs
paths:
  /oauth/token:
    post:
      tags:
      - Authorization
      summary: Issue OAuth 2.0 access token
      description: 'Exchanges FedEx Developer Portal client credentials for an OAuth 2.0

        bearer access token. The returned access token is valid for one hour

        and must be included as a Bearer token on subsequent API calls.'
      security: []
      requestBody:
        required: true
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              required:
              - grant_type
              - client_id
              - client_secret
              properties:
                grant_type:
                  type: string
                  enum:
                  - client_credentials
                  - csp_credentials
                  - client_pc_credentials
                client_id:
                  type: string
                  description: API key issued by the FedEx Developer Portal
                client_secret:
                  type: string
                  description: Secret key issued by the FedEx Developer Portal
      responses:
        '200':
          description: Access token issued
          content:
            application/json:
              schema:
                type: object
                properties:
                  access_token:
                    type: string
                  token_type:
                    type: string
                    example: bearer
                  expires_in:
                    type: integer
                    example: 3600
                  scope:
                    type: string
        '401':
          description: Authentication failure
      operationId: postOauthToken
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'OAuth 2.0 access token returned by POST /oauth/token using

        client_credentials with FedEx Developer Portal credentials.

        '