# FedEx integrations: shipments and return tags

> Create a shipment, create a return tag and send tracking notifications in FedEx, and start a workflow when FedEx sends “Tracking status updated”.

**Canonical page:** https://tray.ai/connectors/fedex-integrations/
**Categories:** Supply chain
**Connects through:** HTTP Connector

## Overview

FedEx is a global shipping carrier whose developer APIs let businesses create shipments and labels, compare rates and transit times, validate addresses and track packages. Tray.ai connects to FedEx through the HTTP Connector, so your workflows can call the FedEx API alongside the rest of your stack.

## Use cases

### Shipments

Read, create, and delete shipments in FedEx from any Tray.ai workflow. The FedEx API covers calls such as create a shipment and validate a shipment.

- Create a shipment
- Validate a shipment
- Cancel a shipment

### Return tags

Create and delete return tags in FedEx from any Tray.ai workflow. The FedEx API covers calls such as create a return tag and cancel a return tag.

- Create a return tag
- Cancel a return tag

### Tracking

Read, create, and manage tracking in FedEx from any Tray.ai workflow. The FedEx API covers calls such as track by tracking number and track by reference.

- Track by tracking number
- Track by reference
- Send tracking notifications

### FedEx events

Start a Tray.ai workflow the moment something happens in FedEx. FedEx sends events such as tracking status updated and estimated delivery window updated to a Tray.ai webhook trigger.

- Tracking status updated
- Estimated delivery window updated

## Challenges Tray.ai solves

### Keeping FedEx credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store FedEx credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the FedEx API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the FedEx API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to FedEx?

Yes. Tray.ai connects to FedEx through the HTTP Connector, which calls the FedEx API directly. Any call the FedEx API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with FedEx?

The FedEx API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated FedEx connector?

FedEx runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated FedEx connector from the FedEx API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/