View Fedex Services

FedEx Tracking Visibility Virtual Sandbox

Access virtual tracking document endpoints for FedEx logistics workflows.

This service provides a virtualized interface for the FedEx Tracking Documents API. It allows developers to simulate the retrieval of shipment tracking information and associated documentation, facilitating the integration of logistics visibility into shipping applications without requiring live connectivity to FedEx production systems.

Use this hosted sandbox to simulate FedEx Tracking Visibility 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 tracking document request payloads, handle shipment status response schemas, test error handling for invalid tracking numbers, and verify the integration of document retrieval workflows within your logistics management platform.

FedEx Tracking Visibility virtual sandbox is up and running!

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

https://fedex-tracking-visibility.mock.beeceptor.com



General

Header NameExample
x-customer-transaction-id"624deea6-b709-470c-8c39-4b5511281492"
content-type*"application/json"
x-locale"en_US"
authorization*"Bearer XXX"
Request Payload
{
  "trackDocumentDetail": {
    "documentFormat": "PDF",
    "documentType": "FREIGHT_BILLING_DOCUMENT"
  },
  "trackDocumentSpecification": [
    {
      "accountNumber": "123456789",
      "trackingNumberInfo": {
        "trackingNumber": "794924591930"
      }
    }
  ]
}
Response Payload
{
  "customerTransactionId": "AnyCo_order123456789",
  "output": {
    "alerts": "TRACKING.DATA.NOTFOUND -  Tracking data unavailable",
    "document": [
      "jsc"
    ],
    "documentFormat": "PNG",
    "documentType": "magna adipisicing incididunt Ut",
    "localization": {
      "languageCode": "en",
      "localeCode": "US"
    }
  },
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492"
}
{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "customerTransactionId": "AnyCo_order123456789",
  "errors": [
    {
      "code": "TRACKING.TRACKINGNUMBER.NOTFOUND",
      "message": "Tracking number cannot be found. Please correct the tracking number and try again."
    }
  ]
}
{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "NOT.AUTHORIZED.ERROR",
      "message": "Access token expired. Please modify your request and try again."
    }
  ]
}
{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "FORBIDDEN.ERROR",
      "message": "We could not authorize your credentials. Please check your permissions and try again."
    }
  ]
}
{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "errors": [
    {
      "code": "NOT.FOUND.ERROR",
      "message": "The resource you requested is no longer available. Please modify your request and try again."
    }
  ]
}
{
  "transactionId": "624deea6-b709-470c-8c39-4b5511281492",
  "customerTransactionId": "AnyCo_order123456789",
  "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",
  "customerTransactionId": "AnyCo_order123456789",
  "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/track/v1/docs.html
fedexlogisticstrackingshippingsupply-chain