Skip to main content
Question

ShipEngine connection issues

  • May 12, 2026
  • 5 replies
  • 21 views

We confirmed ShipEngine is successfully returning valid UPS and FedEx rates outside of Acumatica using direct API testing.

The ShipEngine /v1/rates response completes successfully with no errors and includes valid service codes such as:

  • fedex_ground

  • fedex_priority_overnight

  • ups_ground

  • ups_next_day_air

However, Acumatica 2025 R1 still fails during Get Rates with:
"The given key was not present in the dictionary"

Stack trace:
PX.ExternalCarriersHelper.SOShipmentEntryExtCarriersPXExt.ReplacePackagesWithActualPackages

All returned ShipEngine rates contain:
"package_type": null

Please confirm whether there is a known 2025 R1 ShipEngine connector defect or hotfix related to package mapping/rate parsing within CarrierRatesExtension.

 

Any assistance is greatly appreciated. 

5 replies

mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@connoraaron I think this error typically comes from Customizations only, do you have any customizations or in correct API Mapping?


  • Author
  • Freshman I
  • May 12, 2026

@connoraaron I think this error typically comes from Customizations only, do you have any customizations or in correct API Mapping?

We do have quite a bit of customizations in our tenant. I’m also receiving the same error when I attempted to setup EasyPost. “The given key was not present in the dictionary” 

I’ve confirmed all API connections are setup correctly and communicating with both Ship Engine and EasyPost. 


KrunalDoshi
Varsity III
Forum|alt.badge.img+1
  • Varsity III
  • May 13, 2026

Hi ​@connoraaron,

Have you tried to test the requests in Postman. That will help you understand where is the issue.


Forum|alt.badge.img+9
  • Captain II
  • May 13, 2026

@connoraaron 

 

Do you need to add specific package types/ship via codes for the integration?

 

This usually means, out of a list attribute or another set value, the value requested is not available.


Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • May 13, 2026

@connoraaron I strongly recommend, opening an Acumatica support case by providing the following details.

  • full stack trace
  • raw ShipEngine /v1/rates response
  • proof rates succeed externally

There is a good chance Acumatica may already have:

  • an internal bug ticket
  • private hotfix
  • or upcoming build fix for this.