@okiave from the Developer Release notes from the latest 23R2 beta 2 release: 

Page 13 discusses support for SOAP Based API / WSDL Ends.

@Ellie this is still in progress. I will update everyone here as soon as it is available. 

If you are already using/relying on this integration with an issued API access key, you should not be affected right now and you should be able to continue using it.

@GastonRuggeri  - the update is now available with 2023 R1 Update 13 and 2023 R2 Update 4. 

In case that helps somebody, we used the same project below and just added the next condition to work with both types of plugins:

 if (plugin?.PluginTypeName?.Trim() == typeof(PX.UpsCarrier.UpsCarrier).FullName || 
     plugin?.PluginTypeName?.Trim() == typeof(PX.UpsRestCarrier.UpsRestCarrier).FullName)

@barryk77 It’s not complete yet. We are currently working on the new authentication method and API. As I mentioned earlier, it’s still TBD, but we are hoping to roll these changes to 24R1 (at launch), and minor releases of 23R2, 23R1, and possibly 22R2.

@Omar Ghazi We were affected indirectly, but found a workaround. They have already started deprecating other related features like allowing multiple API accounts in a single UPS CampusShip account, and we therefore want to be on top of this.

As well, we had an upgrade planned for next week but have decided to postpone until it is clear which version will support the new OAuth method. This change in the roadmap has a significant impact on the company.

Thanks for the updates, we look forward to the full resolution!

Jumping in for visibility since yesterday I was asked to look at adding 30 more accounts and remembered this article.

@cdelacruz - Omar updated the document with the production endpoints:

https://acumatica-builds.s3.amazonaws.com/builds/zip/software/addon/ups/UPS+Rest+Configuration.pdf

Re-Summary:

1. If a customer has not acquired a legacy UPS API Key prior to June 5th of this year (2023), they will not be able to get one from UPS.
2. Acumatica's out of the box integration only works with API Keys (and also uses deprecated SOAP api).
3. Any new customers or existing customers that want to use the out of the box UPS Integration and DO NOT already have an API key will NOT be able to use it.
4. Until Acumatica releases an update, they would need to use EasyPost or ShipEngine.
5. They are targeting second half of 2023, and they are hoping to back port this update to older releases, but this has not been determined yet.
6. Any existing customers already using the UPS Integration have until end of May of 2024 to update to a version of Acumatica that supports the RESTful API with OAuth support. This update has yet to be released.

@MattWSM which Acumatica version are you working on?

@alanconroynaw we apologize for the inconvenience, there was a mistake in the documentation. This is available with 2023 R1 Update 13, 2023 R2 Update 4, and later. The documentation has been updated to reflect this. 

In case anyone else struggles like I did (The UPS Developer site is written for developers, which I am not) -API Documents | UPS - United States

I finally found on the right-hand side you can select Try It, then click on the box under Target Server and see the URL’s.

I hope this is correct - it seems to pass the test in the Carrier Integration screen in Acumatica.

I hope this saves someone else the frustration.

@ramakrishnan91 this has been available with 2023 R1 Update 13, 2023 R2 Update 4, and 2024 R1 RC releases and later.

@andrewh22 thank you for your comment! I am curious as to why you reached out to UPS directly and what steps they provided to help you with the configuration steps of the “Create Application” phase. Unless they are very specific to your account, would you be willing to share so we can see if we have an opportunity to improve our documentation to address them for others?

In case anyone is hunting down UPS Developer phone support here it is (as of 2/16/2024):  (800) 247-9035 (option 3, option 3).  They helped me complete the options needed on the ‘Create Application’ step referenced in this article and were more helpful than I expected.

Hi @Irina 

I’m having the same issue with not seeing the UPS REST selection in the dropdown when I try to create the new carrier.

I followed the instructions in your article and updated the license on the ACTIVATE LICENSE screen. However, when I go to the Enable/Disable screen, I don’t see the list of different carriers. This is what I see:

This is the version of Acumatica the customer is on:

Thanks so much for all of the information shared here, it has been so helpful!

@Omar Ghazi Has this been completed yet?
We rely heavily on the current UPS integration for multiple companies.

@Omar Ghazi can you help me find these release notes specific to SOAP API being depricated?
 

@alanconroynaw please create a support ticket with us for this bug that you found in 2023 R1 version. 

Can anyone advise what goes in the callback URL field on the UPS end of this? I noticed someone else posted this screenshot and it was not populated. We have a client setting this up right now and are wondering what to enter here.

 

You dont need anything in there

Just make sure you have the products setup

​@donnadeskins55 are you still experiencing this? If so, please create a case with our support team so we can investigate further.

​

@debbiereed72 Good question! UPS switched to REST-based so please use the PX.UpsRestCarrier.UpsRestCarrier. This is also in the configuration guide (linked with the original post) and the help files will have this information as well.

The PX.UpsCarrier.UpsCarrier as of now will not work any longer and will be removed as an option in a future Acumatica release.

Thank you for sharing your solution with the community @debbiereed72!

@debbiereed72 thank you for bringing this issue up and sorry you had to go through the hunt to find the production URLs. We have updated the configuration guide to include this information. 

THANK YOU, @Omar Ghazi