QuickShip Fedex REST API

Kinetic ERP
1

We received an email from Epicor:

Dear Customer,

FedEx has announced the retirement of its legacy Web Services (SOAP), effective April 1st, 2026. After this date, these services will no longer be available.

To ensure uninterrupted shipping operations, Quick Ship 2025.2 now offers full integration with the FedEx RESTful APIs, including:
• Rating
• Shipping
• LTL (Less-than-Truckload)
• Hazardous Shipments
• Tracking Services

These APIs provide enhanced service capabilities, improved tracking visibility, and a streamlined developer experience.

Please refer to the documents:
• FedEx API Carrier Guide and
• Migrating and Registering an Account with the REST API

For instructions on updating your Quick Ship environment to enable REST API usage.

A couple of questions:

  1. The Fedex API Carrier Guide says that QuickShip 24.2.12 provides REST support, but the email announcement and the Migration document says “With the Quick Ship 2025.2 release, a complete integration with the FedEx REST API is now available”. So: do we need 2025.2, or is 2024.2.12 adequate?
  2. The instructions say that cloud customers must “create a cloud task to update the middleware URL when testing the FedEx REST API in the test environment and enable the UseFedExWebServices app setting for FedEx.” What is a ‘cloud task’??
2 Likes
2

Thanks for posting! We have been QuickShip users since before it was QuickShip and didn’t get an email.

3 Likes
3

A cloud task is a type of ticket you create in EpicCare.

Screenshot 2025-12-12 at 12.45.58 PM
Screenshot 2025-12-12 at 12.45.58 PM1097×321 17.7 KB

4 Likes
4

what is this middleware URL?

5

Something in the Quickship infrastructure; beyond that I have no idea.

6

Correct. Instead of QuickShip communicating directly with our Epicor instances, middleware allows the interception and (if needed) modification of data before it goes out and/or before it comes in. It can also be used to hide implementation details that help secure the connection.

1 Like
8

The middleware they are talking about here is for communication with the carriers. I forgot about this when UPS went to OAuth. In the appsetting there are the endpoints for the middleware. Guessing so that Epicor can update the carrier integrations without having to install new versions of QS.

""FedexSettings": {
  "UseFedExWebServices": false,
  "MiddleWareUri": "https://qs-middleware.epicorsaas.com/FedexAuth"
},
"UPSSettings": {
  "MiddleWareUri": "https://qs-middleware.epicorsaas.com/UPSredirect",
  "UseWebServices": true
},
5 Likes
9

We got the same email and will work on it after the new year.

2 Likes
10

I reached out to Epicor as to why we didn’t get this email as a QuickShip customer. After a few days they figured out they didn’t email on-prem customers. Later that day they did then send the email to on-prem users.

6 Likes
11

Has anyone seen if there is a requirement to upgrade Kinetic to a specific version with this change. I can see upgrading Quick Ship version to a later one, just curious on impact for older Kinetic versions.

1 Like
12

Yeah, I think you need to be on QS version 2025.2.x

I setup our Pilot to REST yesterday for the FedEx small pack account they published in the upgrade guide linked in the email Epicor sent. I also talked to our FedEx acct rep who sent me to a tech to setup REST API on our production account.

2 Likes
13

QS 25.x requires Kinetic 2021.1 or newer for cloud. On-prem 2021.1 or newer if using HTTPS. If just HTTP then 10.1.500 or later

1 Like
14

For the new FedEx REST, yes. QS 25.2.x.

Although in QS 24.2.12 you can add the new FedEx API middleware. Not sure what they changed from 24.2.12 to 25.2.x.

2 Likes
15

I was just going off the version in QS

image
image413×167 6.62 KB

1 Like
16

I think two different questions sort of got put together here.

Required QS version for FedEx REST
Required Kinetic version for the latest QS.

2 Likes
17

The screen cap is out of our Quick Ship. :winking_face_with_tongue:

2 Likes
18

Yes haha, the way I understand it is that you just need to be on a certain version of QS to enable the REST API with FEDEX. I do believe I heard this was the minimum version we needed QS to be at, “2024.2.12” though like @tgwinn said, the way they said “complete” is odd.

2 Likes
19

It’s very odd. Clear as mud, like usual. I’m wondering if not all the FedEx functionality is in their API middleware in 24.2.12. And that’s where the 2025.2 came from.

3 Likes
20

I have no clue.

1 Like
21

From my research it looks like any Kinetic version works with Quick Ship so an upgrade of Kinetic won’t be required for this. Am I missing something?

1 Like