Skip to main content
Question

New FedEx API (FAPI2208) Causing Issues?

  • Sep 16, 2026 5:21 PM UTC
  • 3 replies
  • 7 views

SydSegal

ShipStation recently rolled out a new API when connecting to FedEx called FAPI2208. It appears that this new API went into effect on Monday, Sept. 14th. 

 

Yesterday, the 15th, I created an international label for a customer of mine in the UK (using my connected carrier account - FedEx Connect Plus). Upon label creation, multiple things stood out as incorrect/wrong. First, the label created was not an ETD label (has been an ETD label to this customer for years). Secondly, the label included ISR, which is an Indirect Signature Requirement for delivery (never happened before). The last and biggest issue is that ShipStation now defaults to bill the duties and taxes to the SHIPPER. For all of the years I have been using ShipStation (and my connected FedEx account), the default setting has always been to bill the duties and taxes to the recipient. In the “other shipping options” section of the order screen, you do have the option to “check” the box to bill the duties and taxes to the payor of shipping… but that is not “checked” by default and was not “checked” in this case. 

 

I ended up speaking with a FedEx Engineer who pointed to the fact that his internal system showed that the default setting (for billing duties and taxes) was set by ShipStation to SENDER. I have attached an image to this community thread.

 

Since then, I opened a support case with ShipStation to look into these issues and have them corrected. Aside from the label not defaulting to ETD and implementing a “signature required” option (which could add cost to the label), the fact that the duties and taxes could be billed by default to the shipper of the package could result in unforeseen charges to my (and your) FedEx account. 

 

Lets hope for a good outcome and a fix to these new API issues! If you are in the process of creating FedEx International label (using your connected account), be on the lookout for these issues and whether or not you are being billed (by default) for the duties and taxes!

 

Thanks,

Syd

3 replies

  • Community Manager
  • Sep 16, 2026 5:59 PM UTC

Hi Syd,

Thank you so much for bringing this to our attention with such thorough details. You have outlined critical concerns here, especially regarding duties and taxes billing defaulting to the sender and the missing ETD status.

I will be escalating this directly to our Carrier and Product teams. I will update you as soon as I can. 


SydSegal
  • Author
  • Employee
  • Sep 16, 2026 8:48 PM UTC

 

Hi Syd,

Thank you so much for bringing this to our attention with such thorough details. You have outlined critical concerns here, especially regarding duties and taxes billing defaulting to the sender and the missing ETD status.

I will be escalating this directly to our Carrier and Product teams. I will update you as soon as I can. 

 

Thank you Juan. These are not the only issues as I am seeing more issues occurring when shipping domestically on my Fedex account. I use Smartpost, and after setting the service for multiple orders and then attempting a “batch” print, I am getting a service error. When I went back into the orders I was trying to create labels for, a completely different Fedex Service (Printed Bound Matter) was in place of the Smartpost Parcel option. Image is attached. 

 

I also noticed that shipping Fedex 2 Day resulted in a displayed transit time (within the order label screen) of “3 days”. Clearly incorrect as 2 Day is “2 Days” or the rate will error if its not an area that is able to deliver within the “2 Day” service window.

 

Really frustrating that this API was rolled out without any notice and now ShipStation customers are being used as the proverbial guinea pig to “catch” errors.

 

Thanks


  • Community Manager
  • Sep 16, 2026 10:56 PM UTC

Hey there, 

I want to let you know that you aren’t alone regarding the transit time issue, our engineering and carrier integration teams currently have an open, active investigation into this transit time discrepancy.

I hear your frustration regarding unexpected updates and feeling like you're catching these errors in real time. That is certainly not the experience we want you to have. Please keep letting us know when you run into an issue and I’ll keep sending it over the product team.