Webassist Login

0 views
Skip to first unread message

Janie Leverone

unread,
Aug 3, 2024, 5:10:25 PM8/3/24
to onserniesio

I upgraded to production key. Still getting the same error. Please see the attached UPS screen shot (.pdf) showing production status and the error screen capture. Any help would be appreciated. Any info you need, just ask. Should I be using the 'access key' or the 'developer key' for getting the shipping info? I have been using the access key.

I don't think the special character is the issue. Have you tried contacting UPS support? I'm not sure if it is the developer key or access key. But if you have tried both and get the same issue then I suppose it doesn't matter.

Please provide FTP access and maybe your UPS login and I can try looking into it further. I'd also contact UPS support to see if they can help.

I am unsure how to answer all their requests. I don't know about how to find the 'error being returned in the request'. I am not sure how to verify the TLS level. We haven't changed anything. I can provide the other info to them.

TLS level shouldn't be an issue. Most likely your hosting provider would have handled that. I put all of the information you need to send them in the private area of my response. The errors are what you see on the page when the failure occurs.

UPS replied with the following:
API URLs starting with www.ups.com/ups.app/xml/ or are not currently supported. We are unable to guarantee how long these legacy URLs will remain valid and active.

Please update your URLs as shown in the Developer Guides posted on ups.com. The new URLs begin with

I downloaded the developer guide and tried two different addresses. Got a different error than before (but the same error for both new addresses). Screen shot attached.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages