How do I get a ReceiverKey

Hello:

I'm a developer at NorthForge Innovations and I have registered with this forum and would like to start testing your API.. This is preliminary work in order to figure out how to do APS (Parallels) packaging of your web-services.

I am using the following document ( https://apiforums.easylink.com/system/files/api_basic_guide.pdf
) as my initial guide and just trying to do an Authentication request.

My first step is to try the

the request:

<soapenv:Header>
    <ns1:Request xmlns:ns1="http://ws.easylink.com/RequestResponse/2011/01">
        <ns1:ReceiverKey>http://****/soap/****</ns1:ReceiverKey>
            <ns1:Authentication>
                <ns1:XDDSAuth>
                    <ns1:RequesterID>UserOne</ns1:RequesterID>
                    <ns1:Password>abc123</ns1:Password>
                </ns1:XDDSAuth>
            </ns1:Authentication>
    </ns1:Request>
</soapenv:Header>

I don't know what this reciever key is - but I assume that I need one?

Thanks,

David Balme

Find more posts tagged with

Comments

skamens

The ReceiverKey is really anything you want it to be, although we recommend that it be the same as the URL to which you intend to submit the request.

Have you been provided with credentials to use our test system? If not, you'll need to have those before you can test.

thuneke

From the API documentation:

URI associated with the receiver. Generally this should be the URL to which the request was sent.

The documentation link is on the top right of the page, "API Manuals"

dbalme

Hi Thanks for the quick reply! Great service! :-)

Ok I will put in a receiver key in the way you describe. So the URL I should use is to make the call is:

http://test2messaging.easylink.com/soap/sync/Authenticate/2011/01 ??

I guess I can use that as the ReceiverKey as well? That's assuming I am using the correct URL! :-)

As for the credentials, your company sent us credentials to use for our testing. The credentials are associated with Doug Wilmont our Business Development manager here at NorthForge Innovations. If you would prefer that I use credentials associated with myself, then please let me know and we can start that process.

Actually I tried the above and all I get is (I think) the WSDL as output.

Stepping back, I think what I need is a very simple example to look at. You probably have that I'm just not finding it. The simple example is probably staring me in the face!. I'm sure its me! :-)

Ideally I would like to see a full valid EasyLink SOAP request (in XML form) to your test server. It would be nice to see what URL you post to as well. I can subsitute in Doug's credentials into the SOAP:HEADER.

Currently I am just using a FireFox plugin (Poster) to test my calls into your system - but I'm not getting very far.

Cheers and thanks,

David Balme

skamens

The URL you need to use for submission is https://test2messaging.easylink.com/soap/sync - this is the correct URL for any of the API functions you would need to use.

You can use this as the ReceiverKey if you'd like as well.

The credentials you have are fine - no need to get another set.

We have samples on the forum (just search for "sample"), if you'd like to look at those. Here is a link to a C# Authenticate Project, if that would be helpful.

If you search for "XML Sample" you might find some simple XML samples to look at as well.

Let us know if this helps!

dbalme

I will look at your C# Authenticate example.. Thanks again

metisc

Hello,

I have tried the authentication example, but error always occured ("User authentication not accepted").

I have also put the ReceiverKey as the example above => https://test2messaging.easylink.com/soap/sync

Is there anything I need to run the authentication example run smoothly?

skamens

The ReceiverKey is really anything you want it to be - it is intended to indicate the URL to which you are submitting your request, but it doesn't have any inherent meaning.

Your authentication is not being accepted most likely because the credentials you are using are incorrect, or possibly your credentials are valid on a different system than where you are submitting your request.

In the SOAP header of each result that you get back from the API you should find an element called "ProcessingId". If you can provide us with that, we can look at what is happening with your request.