@rrocket
Sorry, I didn't try to be very clear. I guess at the heart I am saying that I wouldn't even attempt it with Classic ASP. If you were dead-set on it, you could go to the web service site and see a sample request. That would show exactly what needs to be sent for any request.
I personally would not try it with Classic ASP since .NET has support for web services built in. In Visual studio (I use Visual C# Express, but every version has this feature) select "add reference" and on the first page of the wizard you select "Web Reference" and VS does everything else for you, and you can simply reference any part of the web service as if it was a function in your program.
Even if I was doing it in classic ASP, I would make a proxy class to handle the actual web service communication. If you don't want Visual studio you can make a web service proxy from the command line (google "web service proxy", the app that makes the proxy should be on most PCs - it's not too hard, but I don't memorize the steps). Then you just need to get your ASP page to interact with the proxy. I'm not sure how that goes but if you decide to go that direction, let me know and I'll see if I can help. It shouldn't be more than a couple lines of code.
Jared