fedex shipping web service, test account authentication failed

web-services authentication fedex
nico picture nico · May 3, 2010 · Viewed 10.3k times · Source

can't understand why the credentials of my fedex web services test account won't work for the create shipping service and work for the track package service. any ideas?

Answer

Dustin Butler picture Dustin Butler · Jan 6, 2011

This could be due to differences in test and production wdsl. You'll see something like this

<service name="RateService">
    <port name="RateServicePort" binding="ns:RateServiceSoapBinding">
      <s1:address location="https://gatewaybeta.fedex.com:443/web-services/rate"/>
    </port>
</service>

Test is gatewaybeta.fedex.com production is gateway.fedex.com

Edit: Fixed spelling

Related questions

RESTful web service - how to authenticate requests from other services?

I am designing a RESTful web service that needs to be accessed by users, but also other web services and applications. All of the incoming requests need to be authenticated. All communication takes place over HTTPS. User authentication is going …

Read More
SOAPUI Certificate authentication

I am trying to hit a remote web service and check if the service is working. To hit the service I am using SOAPUI client. The first time I tried, I got a 403/Forbidden response. The team developing the remote …

Read More
Forcing Basic Authentication in WebRequest

I am integrating web service that will use an HTTP-POST to request and retrieve data. The remote server requires basic authentication as per RFC 2617 My attempts to authenticate are failing. It fails in that, even though I attach a 'NetworkCredential' …

Read More