Login v3.1

Request a security token, that can be used in the authentication header. This security token is used for authorization for the other calls and must be used in the SOAP Header. How the security token is placed in the header depends on the development environment that you use. See: Example of SecurityToken in SOAP header for some examples.

The SecurityToken has a limited time that it can be used. It is advised to request a new token within 4 hours with a new Login or obtain a new SecurityToken for every session.

Header fields

Fieldname	Description
SOAPAction	Mandatory http://api.everbinding.nl/v3_1/Login

Request fields

Fieldname	Description
ConsumerKey	Mandatory ConsumerKey, provided by the eVerbinding platform.
ConsumerSecret	Mandatory ConsumerSecret, provided by the eVerbinding platform.

Example request

<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
        <Login xmlns="http://api.everbinding.nl/v3_1/">
            <ConsumerKey>6c363164785048334e7251455a66594</ConsumerKey>
            <ConsumerSecret>74425250546761534645747a6952496</ConsumerSecret>
        </Login>
    </S:Body>
</S:Envelope>

Response fields

Fieldname	Description
SecurityToken	Mandatory SecurityToken to used in the SOAP header.

Response 200

<?xml version="1.0" encoding="utf-8"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
        <LoginResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://api.everbinding.nl/v3_1/">
            <SecurityToken>o2S1qTusL29hp3IgMKWsn2I5CFV2LmZ2ZmR2AQp4AGN0BQZmATH3ZwHkAQH1LGL2AGx0VvkiLKI0nS9ho25wMG0vZGtjZQx2BQNjZPVfo2S1qTusqTygMKA0LJ1jCFVkAGN0BQplBQVmVvkiLKI0nS9mnJqhLKE1pzIsoJI0nT9xCFWVGHSQYIAVDGRvYT9uqKEbK3MypaAco249VwRhZPVfo2S1qTusqT9eMJ49VwAnnyIRD0MdAmZ0p3ywpIyYoKqJpTk6qyMVFRqVMyWMVvkiLKI0nS9mnJqhLKE1pzH9VyIPLzgDnayEoHELBJAHESIgI01AHHyGWGWTL0IAWGARVt==</SecurityToken>
        </LoginResponse>
    </SOAP:Body>
</SOAP:Envelope>