FedEx

undefined

Detail	Value
Category	Logistics
Base URL	https://apis.fedex.com
Authentication	OAuth2 Client Credentials
Endpoints	7
Connector key	fedex

Using FedEx in a workflow

1. Go to Connections and click New Connection.
2. Pick FedEx from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET	Tracking
GET	Rate Quotes
GET	Shipments
GET	Address Validation
GET	Transit Times
GET	Pickup
GET	Locations

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Tracking

Detail	Value
Operation ID	tracking_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select tracking_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Rate Quotes

Detail	Value
Operation ID	rate_quotes_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select rate_quotes_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Shipments

Detail	Value
Operation ID	shipments_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select shipments_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Address Validation

Detail	Value
Operation ID	address_validation_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select address_validation_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Transit Times

Detail	Value
Operation ID	transit_times_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select transit_times_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Pickup

Detail	Value
Operation ID	pickup_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select pickup_5.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.

GET

Locations

Detail	Value
Operation ID	locations_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your FedEx connection from the Connection dropdown.
3. In the Operation dropdown, select locations_6.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream FedEx API reference.