FedEx API Authorization Virtual Sandbox

Virtual endpoint for FedEx OAuth 2.0 token generation and credential management.

This virtual endpoint provides a simulated environment for the FedEx OAuth 2.0 authorization flow. Developers can use this to test the exchange of API keys and secrets for access tokens, validate token expiration handling, and verify authentication headers required for subsequent FedEx API requests without hitting live authentication servers.

Use this hosted sandbox to simulate FedEx API Authorization APIs without authentication, API keys, or extra dependencies. Point your code or SDK to the Beeceptor base URL, preferably through an environment variable or feature flag, and switch back to the production API when ready. This keeps your integration code consistent across local development, QA, demos, and production.

Use cases:

Use this sandbox to validate OAuth 2.0 handshake sequences, token request payloads, client credential authentication, and error handling for invalid or expired credentials before integrating with FedEx production identity services.

FedEx API Authorization virtual sandbox is up and running!

Use this sandbox URL as the API base in your code to simulate FedEx API Authorization responses instantly.

`https://fedex-auth.mock.beeceptor.com`

General

POST

/oauth/token

Use this endpoint to request the OAuth token (bearer token) to authorize your application to access FedEx resources. You can pass this bearer token in your subsequent individual FedEx API endpoint requests.<br/><i>Note: FedEx APIs do not support Cross-Origin Resource Sharing (CORS) mechanism.</i>

Header Name	Example
`content-type`*	`"application/x-www-form-urlencoded"`

Request Payload

{
  "grant_type": "client_credentials",
  "client_id": "Your_client_ID",
  "client_secret": "Your_secret"
}

Response Payload

{
  "access_token": "eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3ODI4Njg4MjEsImV4cCI6MTc4MjkwOTcwMCwibmJmIjoxNzU1MjAzNDU0LCJpc3MiOiJPJ0Nvbm5lbGwgR3JvdXAiLCJzdWIiOiIzNDk1MzRlMC1hYjJjLTRkNGItYTYwNC02M2ZlMGU0MWJmNWIiLCJhdWQiOiI5OTU2Mzk3Zi01ZmVjLTQ3NDctOWFmZC1hZmMzZjQ4OWNkZjkiLCJqdGkiOiI4MWUzODYzOS03MTdhLTQ3MzgtYjEwZi1iZDIzNTUwN2JhNmEifQ.yTPp6oPPRfR2jXi7QgZMOwciMgDdSo4tQNjjxinWlRs2OqZYzteY3LHMkYlLsU0J",
  "expires_in": 3600,
  "scope": "CXS",
  "token_type": "bearer"
}

{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "NOT.AUTHORIZED.ERROR",
      "message": "The given client credentials were not valid. Please modify your request and try again."
    }
  ]
}

{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "INTERNAL.SERVER.ERROR",
      "message": "We encountered an unexpected error and are working to resolve the issue. We apologize for any inconvenience. Please check back at a later time."
    }
  ]
}

{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "SERVICE.UNAVAILABLE.ERROR",
      "message": "The service is currently unavailable and we are working to resolve the issue. We apologize for any inconvenience. Please check back at a later time."
    }
  ]
}

Service Homepage: developer.fedex.com/api/en-us/catalog/authorization/v1/docs.html

fedexauthorizationoauthshippinglogistics