Home : Web Services [EN]

Webservices are online applications that allow communication and exchange of data between applications and heterogeneous systems.
Webservices are primarily used by external applications and are based on standard protocols defining communication rules between information systems.
EvenMarketplaces offers associated webservices allowing users to interconnect, the only condition is a valid client account.
This document defines the essential technical specifications to develop an application destined to interface with Neteven’s webservices.
Neteven’s WSDL URL is: https://ws1-4.neteven.com/NWS
Web Services Overview
Interconnexion between your information system and Neteven’s webservices will often be based on developing an applicative module in charge of reading/writing to your information system and sending requests to our servers via Internet.
Information synchronization is triggered by the client either automatically (for Example, via a crontrab or by an update in your IS) or manually (through a button in your back office).
Our webservices use SOAP protocol.
Neteven’ webservices are based on HTTP (or HTTPS), SOAP and WSDL.
SOAP (Simple Object Access Protocol) is a W3C standardized protocol using XML notation allowing the definition of information exchange mechanisms between clients and webservices providers.
The SOAP protocol offers all the advantages in terms of reliability and solidity of a standard protocol, plus use of the available SOAP libraries lightens the workload of the development teams.

Communication with Neteven implies using a SOAP library specific to your programming language, open source libraries are available for almost all programming languages (Python, PHP, JAVA, Visual Basic/.NET, Ruby, etc…)
During the test and integration phase, Neteven’s technical team is available to help you validate the performance of your application.
From a technical point of view, the prerequisites for communicating via webservices with Neteven are:
- Usage of a programming language allowing SOAP communications
- Conformity of your requests with Neteven’s WSDL referential
Aside from the programming language, the communication script will generally follow this pattern:
- Inclusion/upload of the SOAP library
- Library initialisation, if necessary, via Neteven’s WSDL URL
- Authentification (with the login and password of your Neteven account)
- Request execution (requested method + parameters)
- Response treatment
Example of call using a test Echo method (in Iron Python language). This method returns the value sent as a parameter:

These lines of code have sent a SOAP request from the client (script) to the server (webservice Neteven). This request has been automatically generated by the use of the SOAP library, the content of the messages exchanged between the 2 machines being the following:
Content of the message request sent by the webservice client:

Content of the response sent by the server:

In the Annexes, you will find examples of scripts in different programming languages, but this example gives a pretty good idea of the simplicity of the use of Neteven’s webservice through SOAP/WSDL.