Is the document going to get updated. Very hard to understand. Also, do you require authentication in the HEADER or part of the body of the request. I use a program called SoapUI to test the code out before I implement it into our back end software. I am hesitant to do the GetUserKey call with this app as it's not the application that will be actually make the calls later. If it doesn't matter, please let me know.

Also to add, where it states to execute the API, this is only done once? We do not need to include authentication information in future requests?

I agree the documentation is difficult to understand. It will be updated in the future but I don't have a timeframe.



Authentication goes in the header in the SecurityCredential section

Like this:




SoapUI is great for testing. Doing calls in it won't prevent you from doing calls in your application later.


Authentication information must be in all requests. I outlined the basics of the authentication in this other post:
http://forums.networksolutions.com/index.p...ost&p=23804


Hope this helps

(IMG:http://forums.networksolutions.com/style_emoticons/default/thumbsup.gif) Helps immensely! Too bad you're not the tech writer.

One more thing to add. Since we have multiple websites, do we need to get a UserKey for each site?

Tokens are site-specific, you will need one per site.