Click or drag to resize
Upgrading API versions
Print this page

If you wrote applications using a prior version of the API, you can update your projects to the current API by following the instructions below.

This topic contains the following sections:

About Version 2

The SOAP Web Service version 2 portion of Data Exchange by Verizon Connect (TDE) provides a way to access the legacy Fleet Customer API. Note that version 3 is replacing this legacy support with a new interface that is fully native to TDE.

Support for the legacy Customer API through TDE is achieved through two services:

  • TelogisService is the new service, which is expanding as more features are added.
  • LegacyTelogisService has methods and types defined similarly to version 1 of the Customer API.

Together, these services provide the same functionality as version 1 of the Fleet Customer API.

Upgrading from Version 1

If you have applications that still use version 1 of the Fleet Customer API, these steps are needed to transition to version 2.

  1. URL - The URL for the WSDL has changed to this URL, where <customer> is your account name:
    Copy
    https://<customer>.api.telogis.com/v2/<customer>/wsdl
    Throughout this documentation you will see acme.api.telogis.com used as an example fictitious account.
  2. Service objects - Where before you created one instance of the Service object, you now need two Service objects:

    • TelogisService (for logging in)

    • LegacyTelogisService (for all other services)

  3. Login - Change your login code to use the Login method from TelogisService. This method returns a string, which can be assigned to the SessionID of the AuthenticationHeader class.

The following examples demonstrate how to upgrade.

.NET 4

Where in version 1 your code looked like the following:

Copy
Fleet.ServiceSoapClient service = new Fleet.ServiceSoapClient();
string sessionId = service.Login(m_customer, m_user, m_password);
Fleet.AuthenticationHeader header = new Fleet.AuthenticationHeader();
header.SessionID = sessionId;
// header is passed as the first argument to web methods

Now your code should look like the following:

Copy
Fleet.TelogisServiceClient telogisClient = new Fleet.TelogisServiceClient();
string authToken = telogisClient.Login(
string.Format("{0}:{1}", m_customer, m_user), m_password);
Fleet.LegacyTelogisServiceClient service = new Fleet.LegacyTelogisServiceClient();
Fleet.AuthenticationHeader header = new Fleet.AuthenticationHeader();
header.SessionID = authToken;
// header is passed as the first argument to web methods

.NET 2

Where in version 1 your code looked like the following:

Copy
Fleet.Service service = new Fleet.Service();
string sessionId = service.Login(m_customer, m_user, m_password)
Fleet.AuthenticationHeader header = new AuthenticationHeader();
header.SessionID = sessionId;
service.AuthenticationHeaderValue = header;

Now your code should look like the following:

Copy
Fleet.TelogisService telogisService = new Fleet.TelogisService();
string authToken = telogisService.Login(
string.Format("{0}:{1}", m_customer, m_user), m_password);
Fleet.LegacyTelogisService service = new Fleet.LegacyTelogisService();
Fleet.AuthenticationHeader header = new Fleet.AuthenticationHeader();
header.SessionID = authToken;
service.AuthenticationHeaderValue = header;