Skip to main content
Solved

Did anyone else suffer FedEx RestCarrier failure upon upgrade to 24R1?


Hi community,

Our tenant was upgraded to 24R1 on 8/23.  We then found we were unable to pull shipping rates via FedEx.  Checking the FedExRestCarrier plug-in configuration revealed the upgrade had removed all data in the following fields:  Client ID, Client Secret and Login Endpoint.

I logged into our 24R1 upgrade sandbox and noted that the data for those fields was intact.  The upgrade applied differently to the sandbox than it did our tenant.

I re-populated the data in our tenant and clicked on Test Connection, resulting in error:
The test failed. Details: The authentication failed: NOT.FOUND.ERROR The resource you requested is no longer available. Please modify your request and try again.

Obviously, availability of FedEx’s API is not the issue.  And our other FedEx RESTful integrations remain fully functional.

Did anyone else have this issue?  If so, has it been resolved?  We have had a support ticket in since 8/23 with no results.

Thank you,

Best answer by DanielGLL

It seems the answer to our issue is to NOT use the Production URL published by FedEx, which is https://apis.fedex.com and instead replace that with https://apis.fedex.com/oauth/token which does work.  FedEx’s published URL worked for the previous 4 months and suddenly failed on 8/23.  I hope this replacement URL continues to work...

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img

We are getting a similar error on 23R2.  The carrier set up screen tests successful.  Shop for rates tests successfully.  When we go to confirm the shipment, we get:

 


  • Author
  • Jr Varsity I
  • 8 replies
  • Answer
  • August 30, 2024

It seems the answer to our issue is to NOT use the Production URL published by FedEx, which is https://apis.fedex.com and instead replace that with https://apis.fedex.com/oauth/token which does work.  FedEx’s published URL worked for the previous 4 months and suddenly failed on 8/23.  I hope this replacement URL continues to work...


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings