HTTPS over TCP/IP (POST & GET methods)

[tomp]

Have no idea if this is where to post, but I can't decipher the following language:

'Typically, folks use HTTPS over TCP/IP (POST & GET methods) to connect to the API pages to upload & download data, as you would any typical web service. How to do this would depend greatly on the programming language used. For each exclusive URL we include the appropriate method to connect in the page name, so there’s no confusion.'

I had to buy a link into a web-based application to satisfy some potential clients and have to upload a couple of Filemaker-created files to this application. They gave me a '.asp' link and the instructions above. I have no idea what to do. They don't have Filemaker experience.

Any help would be appreciated.

[Zcast]

What? I'm confused. Why would you ever have to buy a link to send them some test files? Something smells rotten in Denmark....

[tomp]

Nope. Not fishy. Just a pain and a nuisance expense.

I have to pay to play - to be able to offer their package as an extension to mine. Market share is at stake! Their package is used by numerous commercial applications like mine. I have potential clients who will convert to me if I can offer their package.

The fee is to set up the accounts and environment for me to test my interface (which includes uploading data for them to use and downloading other data for me to use) before I offer the functionality to my clients through my application. Other applications have jumped through the hoops. I just can't get my feet off the ground.